chore: add bazel build file for cloud_aws #343
Conversation
WalkthroughThis pull request updates the GitHub Actions workflow to trigger on changes in the Changes
Suggested reviewers
Poem
Warning Review ran into problems🔥 ProblemsGitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository. Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
cloud_aws/BUILD.bazel (1)
1-19: Group related dependencies together.Consider organizing dependencies into logical groups with comments:
deps = [ + # AWS SDK dependencies maven_artifact("software.amazon.awssdk:dynamodb"), maven_artifact("software.amazon.awssdk:regions"), maven_artifact("software.amazon.awssdk:aws-core"), maven_artifact("software.amazon.awssdk:sdk-core"), maven_artifact("software.amazon.awssdk:utils"), + # Scala dependencies scala_artifact("org.scala-lang.modules:scala-collection-compat"), + # Utility dependencies maven_artifact("com.google.guava:guava"), maven_artifact("org.slf4j:slf4j-api"), + # Internal dependencies "//spark:lib", "//online:lib", "//api:lib", "//api:thrift_java", ],
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)
📒 Files selected for processing (5)
.github/workflows/test_scala_non_spark.yaml(3 hunks)cloud_aws/BUILD.bazel(1 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala(2 hunks)cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala(2 hunks)tools/build_rules/dependencies/maven_repository.bzl(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: non_spark_tests
- GitHub Check: bazel_config_tests
- GitHub Check: enforce_triggered_workflows
- GitHub Check: scala_compile_fmt_fix
🔇 Additional comments (5)
cloud_aws/BUILD.bazel (2)
43-50: LGTM!Test suite configuration is properly set up with necessary dependencies and JVM flags.
21-33: Verify DynamoDBLocal version compatibility.Check if version 2.5.1 of DynamoDBLocal is compatible with AWS SDK 2.30.13.
✅ Verification successful
🌐 Web query:
What is the latest version of DynamoDBLocal that is compatible with AWS SDK 2.30.13?💡 Result:
The latest compatible version of **DynamoDB Local** with AWS SDK for Java **v2.x** (including **v2.30.13**) is **v2.x**, specifically **version ≥2.0**. Here’s why: ### Compatibility Overview 1. **SDK v2 Support**: - Starting with **DynamoDB Local v1.16+** (released May 2021), AWS added experimental support for SDK v2 via server mode[5][10]. - Full native support arrived in **DynamoDB Local v2.x** (released July 2023), which migrated to Jakarta EE namespaces and dropped legacy javax dependencies[1][8][9]. ### Key Versions | DynamoDB Local Version | AWS SDK Compatibility | Notes | |------------------------|-----------------------|-------| | **v1.x** (Legacy) | Partial support via server mode | Requires manual configuration[5][10]. End-of-life: January 2025[10]. | | **v2.x** (Current) | Full native support | Uses Jakarta EE namespaces and aligns with SDK v2 standards[8][9]. | ### Recommendations - Use **DynamoDB Local v2.x** (latest: **v2.5+**) for seamless compatibility with AWS SDK for Java **v2.x**, including `CreateTableRequest` and other modern APIs[6][8]. - Avoid v1.x unless maintaining legacy codebases[10]. For example, in Maven projects: ```xml <dependency> <groupId>com.amazonaws</groupId> <artifactId>DynamoDBLocal</artifactId> <version>2.5+</version> </dependency> ``` This ensures compatibility with AWS SDK v2 features like enhanced client operations[6][8]. Citations: - 1: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocalHistory.html - 2: https://aws.amazon.com/about-aws/whats-new/2021/05/amazon-dynamodb-local-now-supports-the-aws-sdk-for-java-2-x/ - 3: https://github.com/awslabs/amazon-dynamodb-local-samples/issues/14 - 4: https://www.serverless.com/plugins/serverless-dynamodb-local - 5: https://github.com/aws/aws-sdk-java-v2/issues/982 - 6: https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/dynamodb/model/CreateTableRequest.html - 7: https://github.com/awslabs/amazon-dynamodb-local-samples/issues/18 - 8: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html - 9: https://mvnrepository.com/artifact/com.amazonaws/DynamoDBLocal/2.0.0 - 10: https://repost.aws/ko/articles/AR3JPKxzfSQ--ZhOwXMKPZyg/amazon-dynamodb-local-1-x-end-of-support-is-january-2025?sc_ichannel=ha&sc_ilang=en&sc_isite=repost&sc_iplace=hp&sc_icontent=AR3JPKxzfSQ--ZhOwXMKPZyg&sc_ipos=4
DynamoDBLocal version compatibility verified.
• DynamoDBLocal v2.x (preferably v2.5+) is fully compatible with AWS SDK 2.30.13.
• Version 2.5.1 aligns with these compatibility requirements.tools/build_rules/dependencies/maven_repository.bzl (1)
84-92: Verify AWS SDK version.Check if 2.30.13 is the latest stable version of the AWS SDK.
.github/workflows/test_scala_non_spark.yaml (2)
15-15: LGTM!Path triggers for cloud_aws are properly added to both push and pull_request events.
Also applies to: 30-30
115-120: LGTM!Test step configuration matches other modules and uses correct target.
| sys.env.get("AWS_DEFAULT_REGION").foreach { region => | ||
| try { | ||
| builder = builder.region(Region.of(region)) | ||
| builder // = builder.region(Region.of(region)) |
There was a problem hiding this comment.
Restore or remove commented code.
The region setting is commented out which could affect AWS operations. Either restore it or remove it completely.
- builder // = builder.region(Region.of(region))
+ builder = builder.region(Region.of(region))📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| builder // = builder.region(Region.of(region)) | |
| builder = builder.region(Region.of(region)) |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala (1)
5-5: Add ScalaDoc for the class.Add class-level documentation explaining the purpose and AWS Livy integration details.
+/** + * Submits Spark jobs to an AWS EMR cluster using Apache Livy REST API. + */ class LivySubmitter extends JobSubmitter {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)
📒 Files selected for processing (1)
cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: scala_compile_fmt_fix
- GitHub Check: non_spark_tests
| override def submit(jobType: JobType, | ||
| jobProperties: Map[String, String], | ||
| files: List[String], | ||
| args: String*): String = ??? | ||
|
|
There was a problem hiding this comment.
Implement required methods.
All three overridden methods are unimplemented. Please provide implementations for:
- submit: Job submission via Livy REST API
- status: Job status checking
- kill: Job termination
Would you like me to help implement these methods with proper AWS Livy integration?
Also applies to: 12-13, 14-15
tchow-zlai
force-pushed
the
tchow/aws-infra
branch
from
f26eafc to
afb2715
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
cloud_aws/BUILD.bazel (1)
37-37: Avoid duplicate source patterns.Same pattern
src/test/**/*.scalaused in both test_lib and tests.- srcs = glob(["src/test/**/*.scala"]), + srcs = glob(["src/test/scala/lib/**/*.scala"]),Also applies to: 45-45
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)
📒 Files selected for processing (6)
.github/workflows/test_scala_non_spark.yaml(3 hunks)cloud_aws/BUILD.bazel(1 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala(2 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala(1 hunks)cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala(2 hunks)tools/build_rules/dependencies/maven_repository.bzl(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala
- .github/workflows/test_scala_non_spark.yaml
- cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala
- tools/build_rules/dependencies/maven_repository.bzl
- cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: non_spark_tests
- GitHub Check: scala_compile_fmt_fix
🔇 Additional comments (2)
cloud_aws/BUILD.bazel (2)
33-33: Verify _CIRCE_DEPS and _SCALA_TEST_DEPS are defined.❌ Verification inconclusive
🏁 Script executed:
#!/bin/bash # Search for deps definitions rg "_CIRCE_DEPS|_SCALA_TEST_DEPS" --type bazelLength of output: 306
Review Verification: Definitions Found
The search shows that while _CIRCE_DEPS and _SCALA_TEST_DEPS are referenced in multiple BUILD files, no explicit definitions were located in the BUILD files. However, these variables are likely defined in a separate .bzl file, as is common in Bazel setups. Please verify that they are indeed defined in the referenced .bzl file (or an equivalent centralized dependency configuration).
6-11: Pin AWS SDK versions for reproducible builds.❌ Verification inconclusive
🏁 Script executed:
#!/bin/bash # Check for version constraints in WORKSPACE file rg "software\.amazon\.awssdk" -A 2Length of output: 6481
AWS SDK versions are already pinned elsewhere.
cloud_aws/BUILD.bazelintentionally omits explicit versions.- Versions are set centrally in
tools/build_rules/dependencies/maven_repository.bzl(e.g. "2.30.13").Likely an incorrect or invalid review comment.
| name = "tests", | ||
| srcs = glob(["src/test/**/*.scala"]), | ||
| # defined in prelude_bazel file | ||
| jvm_flags = _JVM_FLAGS_FOR_ACCESSING_BASE_JAVA_CLASSES, |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify _JVM_FLAGS_FOR_ACCESSING_BASE_JAVA_CLASSES is defined.
🏁 Script executed:
#!/bin/bash
# Search for JVM flags definition
rg "_JVM_FLAGS_FOR_ACCESSING_BASE_JAVA_CLASSES" --type bazelLength of output: 459
Undefined _JVM_FLAGS_FOR_ACCESSING_BASE_JAVA_CLASSES identified:
The flag is referenced in multiple BUILD files (cloud_aws, cloud_gcp, flink, online, spark) but no definition is found in the repository. Please define it or update its references.
tchow-zlai
force-pushed
the
tchow/aws-infra
branch
2 times, most recently
from
8ba0cd1 to
3415cca
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala (1)
7-15:⚠️ Potential issueImplement required methods.
All three overridden methods are unimplemented.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)
📒 Files selected for processing (6)
.github/workflows/test_scala_non_spark.yaml(3 hunks)cloud_aws/BUILD.bazel(1 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala(2 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/LivySubmitter.scala(1 hunks)cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala(2 hunks)tools/build_rules/dependencies/maven_repository.bzl(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala
- cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala
- tools/build_rules/dependencies/maven_repository.bzl
- .github/workflows/test_scala_non_spark.yaml
- cloud_aws/BUILD.bazel
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: bazel_config_tests
- GitHub Check: scala_compile_fmt_fix
- GitHub Check: non_spark_tests
- GitHub Check: enforce_triggered_workflows
- GitHub Check: enforce_triggered_workflows
|
|
||
| import ai.chronon.spark.{JobSubmitter, JobType} | ||
|
|
||
| class LivySubmitter extends JobSubmitter { |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add AWS Livy client initialization.
Initialize Livy client in constructor or companion object.
-class LivySubmitter extends JobSubmitter {
+class LivySubmitter(
+ livyEndpoint: String,
+ awsRegion: String
+) extends JobSubmitter {
+ private val livyClient = LivyClient.builder()
+ .endpoint(livyEndpoint)
+ .region(awsRegion)
+ .build()📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| class LivySubmitter extends JobSubmitter { | |
| class LivySubmitter( | |
| livyEndpoint: String, | |
| awsRegion: String | |
| ) extends JobSubmitter { | |
| private val livyClient = LivyClient.builder() | |
| .endpoint(livyEndpoint) | |
| .region(awsRegion) | |
| .build() | |
| // Other methods and implementations... | |
| } |
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]> Co-authored-by: Thomas Chow <[email protected]>
Co-authored-by: Thomas Chow <[email protected]>
tchow-zlai
force-pushed
the
tchow/aws-infra
branch
from
0b40370 to
697e78b
Compare
Co-authored-by: Thomas Chow <[email protected]>
tchow-zlai
requested review from
nikhil-zlai,
varant-zlai,
piyush-zlai,
chewy-zlai,
david-zlai and
kumar-zlai
Co-authored-by: Thomas Chow <[email protected]>
cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala
Outdated
Show resolved
Hide resolved
Co-authored-by: Thomas Chow <[email protected]>
|
@kumar-zlai I think the flags are still not working for setting java build version - any thoughts here? |
Co-authored-by: Thomas Chow <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala (1)
121-121: Timeout increased from 1s to 1min.The increased timeout is good for reliability, but consider extracting it as a constant.
+ private val DefaultTimeout = 1.minute - Await.result(kvStore.multiPut(putReqs), 1.minute) + Await.result(kvStore.multiPut(putReqs), DefaultTimeout)Also applies to: 127-127, 134-134, 154-154, 162-164, 184-184, 190-190
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)
📒 Files selected for processing (4)
.bazelrc(1 hunks).github/workflows/test_scala_non_spark.yaml(3 hunks)cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala(2 hunks)cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala(7 hunks)
✅ Files skipped from review due to trivial changes (1)
- .bazelrc
🚧 Files skipped from review as they are similar to previous changes (2)
- .github/workflows/test_scala_non_spark.yaml
- cloud_aws/src/main/scala/ai/chronon/integrations/aws/AwsApiImpl.scala
🧰 Additional context used
🧠 Learnings (1)
cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala (3)
Learnt from: piyush-zlai
PR: zipline-ai/chronon#33
File: cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala:175-175
Timestamp: 2024-11-12T09:38:33.532Z
Learning: Hardcoding future timestamps in tests within `DynamoDBKVStoreTest.scala` is acceptable when data is generated and queried within the same time range, ensuring the tests remain valid over time.
Learnt from: piyush-zlai
PR: zipline-ai/chronon#33
File: cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala:82-89
Timestamp: 2024-11-12T09:38:33.532Z
Learning: DynamoDB does not create duplicate tables when attempting to create a table that already exists, so checking for duplicates in tests is redundant.
Learnt from: piyush-zlai
PR: zipline-ai/chronon#33
File: cloud_aws/src/main/scala/ai/chronon/integrations/aws/DynamoDBKVStoreImpl.scala:245-260
Timestamp: 2024-11-12T09:38:33.532Z
Learning: In `DynamoDBKVStoreImpl.scala`, refactoring methods like `extractTimedValues` and `extractListValues` to eliminate code duplication is discouraged if it would make the code more convoluted.
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: bazel_config_tests
- GitHub Check: non_spark_tests
- GitHub Check: scala_compile_fmt_fix
- GitHub Check: enforce_triggered_workflows
- GitHub Check: enforce_triggered_workflows
🔇 Additional comments (3)
cloud_aws/src/test/scala/ai/chronon/integrations/aws/DynamoDBKVStoreTest.scala (3)
3-22: LGTM! Import organization looks clean.The imports are well-organized and grouped logically.
24-30: Good encapsulation of test utilities.Moving case classes to DDBTestUtils object improves code organization.
Also applies to: 33-39
237-237: Fixed comparison in validateExpectedListResponse.The comparison
mSeq.length <= maxElementsis correct for validating paginated results.
| override def afterAll(): Unit = { | ||
| // client.close() | ||
| // server.stop() | ||
| } |
There was a problem hiding this comment.
Cleanup code is commented out.
The cleanup code in afterAll should be uncommented to properly release resources.
- override def afterAll(): Unit = {
-// client.close()
-// server.stop()
- }
+ override def afterAll(): Unit = {
+ client.close()
+ server.stop()
+ }📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| override def afterAll(): Unit = { | |
| // client.close() | |
| // server.stop() | |
| } | |
| override def afterAll(): Unit = { | |
| client.close() | |
| server.stop() | |
| } |
Co-authored-by: Thomas Chow <[email protected]>
## Summary
- Adding new BUILD for cloud_aws
- Adding the above to the CI/CD
## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced AWS integration with a new library for AWS functionality and
a framework for job submission.
- Introduced a new utility for managing job submissions, statuses, and
terminations.
- Added dedicated triggers for cloud modules to improve workflow
automation.
- **Tests**
- Improved testing coverage with additional utilities for validating
cloud functionalities and increased timeout settings for asynchronous
operations.
- **Chores**
- Updated dependency configurations to incorporate essential AWS SDK
components.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->
---------
Co-authored-by: Thomas Chow <[email protected]>
## Summary
- Adding new BUILD for cloud_aws
- Adding the above to the CI/CD
## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced AWS integration with a new library for AWS functionality and
a framework for job submission.
- Introduced a new utility for managing job submissions, statuses, and
terminations.
- Added dedicated triggers for cloud modules to improve workflow
automation.
- **Tests**
- Improved testing coverage with additional utilities for validating
cloud functionalities and increased timeout settings for asynchronous
operations.
- **Chores**
- Updated dependency configurations to incorporate essential AWS SDK
components.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->
---------
Co-authored-by: Thomas Chow <[email protected]>
## Summary
- Adding new BUILD for cloud_aws
- Adding the above to the CI/CD
## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced AWS integration with a new library for AWS functionality and
a framework for job submission.
- Introduced a new utility for managing job submissions, statuses, and
terminations.
- Added dedicated triggers for cloud modules to improve workflow
automation.
- **Tests**
- Improved testing coverage with additional utilities for validating
cloud functionalities and increased timeout settings for asynchronous
operations.
- **Chores**
- Updated dependency configurations to incorporate essential AWS SDK
components.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->
---------
Co-authored-by: Thomas Chow <[email protected]>
## Summary
- Adding new BUILD for cloud_aws
- Adding the above to the CI/CD
## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced AWS integration with a new library for AWS functionality and
a framework for job submission.
- Introduced a new utility for managing job submissions, statuses, and
terminations.
- Added dedicated triggers for cloud modules to improve workflow
automation.
- **Tests**
- Improved testing coverage with additional utilities for validating
cloud functionalities and increased timeout settings for asynchronous
operations.
- **Chores**
- Updated dependency configurations to incorporate essential AWS SDK
components.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->
---------
Co-authored-by: Thomas Chow <[email protected]>
## Summary
- Adding new BUILD for cloud_aws
- Adding the above to the CI/CD
## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced AWS integration with a new library for AWS functionality and
a framework for job submission.
- Introduced a new utility for managing job submissions, statuses, and
terminations.
- Added dedicated triggers for cloud modules to improve workflow
automation.
- **Tests**
- Improved testing coverage with additional utilities for validating
cloud functionalities and increased timeout settings for asynchronous
operations.
- **Chores**
- Updated dependency configurations to incorporate essential AWS SDK
components.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to traour clients
the status of staour clientss when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->
---------
Co-authored-by: Thomas Chow <[email protected]>
Summary
Checklist
Summary by CodeRabbit