v0.25.1

🐛 Bug Fixes

fix: Multi-AZ EFS mount targets in same AZ subnets @brent-anyscale (#60)

When creating EFS mount targets in subnets that are in the same AZ, the mount target configuration would fail. While Anyscale does not recommend using multiple subnets in the same AZ, this fixes the scenario where the submodule would fail.

On branch brent/fix-efs-sameazsubnets
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
modified: main.tf
modified: modules/aws-anyscale-securitygroups/main.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.25.0

🚀 Enhancements

upd: IAM and S3 Policy Updates for new dependency tracking @brent-anyscale (#58)

Anyscale is releasing a new dependency tracking feature for Ansycale Workspaces. This new functionality requires additional permissions for the S3 bucket including:

• s3:ListBucketMultipartUploads
• s3:ListMultipartUploadParts
• s3:AbortMultipartUpload
• s3:GetBucketLocation

On branch brent/upd-s3-access Changes to be committed: - modified: CHANGELOG.md - modified: modules/aws-anyscale-iam/s3-bucket-access.tmpl - modified: modules/aws-anyscale-s3-policy/predefined_s3_policy.tpl

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.24.0

🚀 Enhancements

upd: IAM Submodule - Updated IAM Policy for Control Plane Role @brent-anyscale (#57)

When passing in an Anyscale CloudID to the aws-anyscale-iam submodule, the
policy for the Control Plane Role will now restrict access (based on tags) to
EBS Volume creation and attachments, and EC2 Instance Profile management.

On branch brent/upd-iam
Changes to be committed:
modified: CHANGELOG.md
modified: modules/aws-anyscale-iam/iam-policies-data.tf

## Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):
  Update to least-privilege IAM Policy for the Control Plane

Does this introduce a breaking change?

• Yes
• No

v0.23.1

📚 Documentation/Examples

upd: README and Variables - general cleanup @brent-anyscale (#56)

On branch brent/upd-root-readme
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
modified: variables.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.23.0

🚀 Enhancements

upd: aws-anyscale-iam - add assumption policy override @brent-anyscale (#55)

In specific situations, the IAM DataPlane Role may need a different assumption policy. This can be used for identity pass through, where an Anyscale Cluster can re-assume the role already in place with the email address of the user who started the cluster as additional data.

Additional updates include:

• gitignore updates
• pre-commit updates
• updates to tests for aws-anyscale-iam
• Various scanning exceptions

On branch brent/iam-clusternodepolicy
Changes to be committed:
modified: .gitignore
modified: .pre-commit-config.yaml
modified: README.md
modified: examples/anyscale-v2-kitchensink/README.md
modified: examples/anyscale-v2-kitchensink/variables.tf
modified: main.tf
modified: modules/aws-anyscale-iam/README.md
modified: modules/aws-anyscale-iam/eks-iam-main.tf
new file: modules/aws-anyscale-iam/examples/data.tf
renamed: modules/aws-anyscale-iam/test/anyscale-test/main.tf -> modules/aws-anyscale-iam/examples/main.tf
renamed: modules/aws-anyscale-iam/test/anyscale-test/outputs.tf -> modules/aws-anyscale-iam/examples/outputs.tf
renamed: modules/aws-anyscale-iam/test/anyscale-test/variables.tf -> modules/aws-anyscale-iam/examples/variables.tf
renamed: modules/aws-anyscale-iam/test/anyscale-test/versions.tf -> modules/aws-anyscale-iam/examples/versions.tf
modified: modules/aws-anyscale-iam/main.tf
deleted: modules/aws-anyscale-iam/test/README.md
modified: modules/aws-anyscale-iam/variables.tf
modified: modules/aws-anyscale-s3/README.md
modified: modules/aws-anyscale-s3/main.tf
modified: modules/aws-anyscale-securitygroups/README.md
modified: modules/aws-anyscale-securitygroups/main.tf
modified: modules/aws-anyscale-vpc/README.md
modified: modules/aws-anyscale-vpc/main.tf
modified: variables.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.22.2

🐛 Bug Fixes

upd: aws-anyscale-s3-policy module to support custom policies @brent-anyscale (#54)

The custom policies were not being passed from the root module to the sub-module. This change adds the ability to pass in custom modules from the root module.

This may replace the existing S3 Policy on the Anyscale S3 bucket

Additional updates include a large rewrite of the s3-policy module to include:

• Pre-defined S3 Policy template file
• Renamed variables to be more descriptive
• Reworked examples/tests

Lastly, this also includes an updated kitchensink example to show how to use the custom policy feature.

On branch brent/update-s3policy
Changes to be committed:
modified: .pre-commit-config.yaml
modified: README.md
modified: examples/anyscale-v2-kitchensink/README.md
modified: examples/anyscale-v2-kitchensink/main.tf
modified: examples/anyscale-v2-kitchensink/variables.tf
modified: main.tf
modified: modules/aws-anyscale-s3-policy/README.md
deleted: modules/aws-anyscale-s3-policy/examples/README.md
modified: modules/aws-anyscale-s3-policy/examples/main.tf
modified: modules/aws-anyscale-s3-policy/examples/outputs.tf
modified: modules/aws-anyscale-s3-policy/examples/variables.tf
modified: modules/aws-anyscale-s3-policy/main.tf
new file: modules/aws-anyscale-s3-policy/predefined_s3_policy.tpl
modified: modules/aws-anyscale-s3-policy/test/README.md
deleted: modules/aws-anyscale-s3-policy/test/anyscale-test/main.tf
deleted: modules/aws-anyscale-s3-policy/test/anyscale-test/outputs.tf
deleted: modules/aws-anyscale-s3-policy/test/anyscale-test/variables.tf
deleted: modules/aws-anyscale-s3-policy/test/anyscale-test/versions.tf
modified: modules/aws-anyscale-s3-policy/variables.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

This may replace the S3 policy on the existing S3 bucket

v0.22.1

🚀 Enhancements

Initial EKS Support for Anyscale on Kubernetes @brent-anyscale (#52)

This PR includes the required changes to support the initial release of Anyscale running on EKS. This should be considered a beta release and additional updates will be coming.

NOT YET DONE:

• Minimal IAM Role for the Control Plane when using Anyscale Kubernetes.

🐛 Bug Fixes

fix: EKS Nodegroups - Use pinned version from Scaling Template @brent-anyscale (#53)

The original release of this used $LATEST which was causing each terraform apply to recalculate the launch template and update the nodegroups, even when there were no changes.

This now utilizes the latest_version attribute from the aws_launch_template

Changes to be committed:
modified: CHANGELOG.md
modified: modules/aws-anyscale-eks-nodegroups/main.tf
modified: modules/aws-anyscale-iam/iam-policies-data.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.22.0

🚀 Enhancements

Initial EKS Support for Anyscale on Kubernetes @brent-anyscale (#52)

This PR includes the required changes to support the initial release of Anyscale running on EKS. This should be considered a beta release and additional updates will be coming.

NOT YET DONE:

• Minimal IAM Role for the Control Plane when using Anyscale Kubernetes.

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.21.1

📚 Documentation/Examples

fix: Example documentation for KMS @brent-anyscale (#51)

Removed reference to us-east-2 in KMS example.
General cleanup on language and formatting in KMS example.

On branch brent/example-kms-cleanup
Changes to be committed:
modified: examples/anyscale-v2-kms/README.md
modified: examples/anyscale-v2-kms/main.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

v0.21.0

🚀 Enhancements

Update IAM Policies for Anyscale Services @brent-anyscale (#49)

Allow Anyscale Services an additional IAM Permission for Cloudformation which will allow the service to add version HTTP Headers.

On branch brent/update-iam
Changes to be committed:
modified: CHANGELOG.md
modified: modules/aws-anyscale-iam/iam-policies-data.tf

Pull request checklist

Please check if your PR fulfills the following requirements:

• pre-commit has been run
• Tests for the changes have been added (for bug fixes / features)
• All tests passing
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Pull Request Type

• Bugfix
• New feature
• Refactoring (no functional changes)
• Documentation change
• Other (please describe):

Does this introduce a breaking change?

• Yes
• No

Other information