Releases: anyscale/terraform-aws-anyscale-cloudfoundation-modules
v0.19.4
📚 Documentation/Examples
upd: README.md and CHANGELOG.md @brent-anyscale (#45)
Added missing releases to the CHANGELOG
Updated the README with additional information on modules and how to use them.
On branch brent/readmeupd
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
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.19.3
upd: update cors rules in aws-anyscale-s3 module @brent-anyscale (#44)
With some upcoming changes to the Anyscale Web Console,
there are changes for the CORS rules for the S3 bucket.
Additional cleanup work done on the aws-anyscale-s3 unit tests, removing the
unused Go unit tests.
Changes to be committed:
modified: modules/aws-anyscale-s3/README.md
modified: modules/aws-anyscale-s3/test/README.md
deleted: modules/aws-anyscale-s3/test/go.mod
deleted: modules/aws-anyscale-s3/test/go.sum
deleted: modules/aws-anyscale-s3/test/terraform_aws_anyscale_s3_test.go
modified: modules/aws-anyscale-s3/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.19.2
upd: Go Unit tests removed in favor of Python E2E test @brent-anyscale (#43)
The Go Unit tests have not been updated in some time. Current process is to use the Python E2E tests which also now includes testing of creating an Anyscale Cloud and Workspace/Service based on the Terraform resources created.
On branch brent/removedefaultgotests
Changes to be committed:
modified: README.md
deleted: anyscale_v2_00_test.go
deleted: anyscale_v2_01_existing_vpc_test.go
deleted: anyscale_v2_02_private_subnets_test.go
deleted: anyscale_v2_03_common_name_test.go
deleted: anyscale_v2_04_create_endpoints_test.go
deleted: anyscale_v2_05_e2e_public_test.go
deleted: anyscale_v2_06_e2e_private_test.go
deleted: go.mod
deleted: go.sum
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.19.1
🐛 Bug Fixes
fix: Existing S3 bucket functionality @brent-anyscale (#41)
Using an existing S3 bucket via the example anyscale-v2-existing-s3
was broken with the latest versions of Terraform due to an invalid IAM policy reference to the S3 bucket name. This fixes that - and updates the example to provide a working output command that can be used to register an Anyscale Cloud.
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
v0.19.0
🚀 Enhancements
feat: Update outputs for EFS and VPC sub-modules @brent-anyscale (#40)
Added additional outputs to the EFS and VPC sub-modules to make it easier to register Anyscale Clouds in certain situations. These outputs were exposed in the root module as well.
On branch brent/outputupdates
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
modified: modules/aws-anyscale-efs/README.md
modified: modules/aws-anyscale-efs/outputs.tf
modified: modules/aws-anyscale-vpc/README.md
modified: modules/aws-anyscale-vpc/outputs.tf
modified: outputs.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
📚 Documentation/Examples
feat: Update outputs for EFS and VPC sub-modules @brent-anyscale (#40)
Added additional outputs to the EFS and VPC sub-modules to make it easier to register Anyscale Clouds in certain situations. These outputs were exposed in the root module as well.
On branch brent/outputupdates
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
modified: modules/aws-anyscale-efs/README.md
modified: modules/aws-anyscale-efs/outputs.tf
modified: modules/aws-anyscale-vpc/README.md
modified: modules/aws-anyscale-vpc/outputs.tf
modified: outputs.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
v0.18.3
📚 Documentation/Examples
[upd] Cleanup of example outputs @brent-anyscale (#39)
Cleaned up the example outputs so that the anyscale cloud registration command is easier to read and copy/paste.
Additional updates to pre-commit and tflint versions and an update to the pull request template.
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):
Cleanup of example outputs, pre-commit and tflint updates
Does this introduce a breaking change?
- Yes
- No
v0.18.2
🐛 Bug Fixes
[upd] kitchensink example and e2e test AWS Provider versions @brent-anyscale (#38)
The AWS Provider version 5.17.0 has a bug which causes s3 bucket deletion via terraform to fail. This commit updates the kitchensink example and the e2e unit test to use the AWS Provider version 5.16.x.
It also updates pre-commit-config to not update to the lates 5.0 version.
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 (for AWS Terraform Provider bug)
- New feature
- Refactoring (no functional changes)
- Documentation change
- Other (please describe):
Does this introduce a breaking change?
- Yes
- No
v0.18.1
🐛 Bug Fixes
[fix] IAM Policy for Cloudwatch Log/Metric Access @brent-anyscale (#37)
Bugfix - IAM SubModule
In testing with the latest documentation for sending logs to
Cloudwatch, we are
no longer enforcing "Organzation" as part of the namespace. This
commit removes that requirement.
On branch brent/iam-cloudwatch-bugfix
Changes to be committed:
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.18.0
🚀 Enhancements
[add] aws-anyscale-memorydb sub-module @brent-anyscale (#36)
The aws-anyscale-memorydb sub-module is a Terraform module that creates a MemoryDB cluster and related resources. This is used with Anyscale Services for Head node fault tolerance by implementing a Redis cluster.
This is an optional sub-module and is not required for Anyscale or Anyscale Services. If you enable this sub-module, it will take 5-15 minutes to create the MemoryDB cluster.
Example of this sub-module in use can be seen in the anyscale-v2-kitchensink
example and the anyscale-v2-privatesubnets
.
🐛 Bug Fixes
This release includes a bugfix for names of subnets in the aws-anyscale-vpc when certain variables are set.
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.17.0
🚀 Enhancements
[upd] aws-anyscale-iam: Add Optional SecretsManager IAM policy @brent-anyscale (#35)
This commit adds a new IAM policy for SecretsManager. This policy allows passing in a new parameter with a list of secrets - as well as a KMS key to use (optional). This policy is then assigned to the Cluster Node IAM role. This allows the cluster to read the secret which is then used for BYOD (Bring Your Own Docker) images that are in private, password protected repositories.
Additional updates include a new example named kitchensink (WIP), updates to the latest Terraform and AWS Provider versions. There are also updates to the unit tests with the plan to automate building the resources, deploying an Anyscale Cloud, using Functional Verification, and then destroying the resources as part of an automated github action (also a WIP).
On branch brent/iam-secrets
Changes to be committed:
modified: .tflint.hcl
modified: CHANGELOG.md
modified: README.md
deleted: examples/anyscale-v2-createendpoints/README.md
deleted: examples/anyscale-v2-createendpoints/main.tf
deleted: examples/anyscale-v2-createendpoints/outputs.tf
modified: examples/anyscale-v2-existing-vpc/main.tf
new file: examples/anyscale-v2-kitchensink/README.md
new file: examples/anyscale-v2-kitchensink/main.tf
new file: examples/anyscale-v2-kitchensink/outputs.tf
renamed: examples/anyscale-v2-createendpoints/variables.tf -> examples/anyscale-v2-kitchensink/variables.tf
renamed: examples/anyscale-v2-createendpoints/versions.tf -> examples/anyscale-v2-kitchensink/versions.tf
modified: main.tf
modified: modules/aws-anyscale-efs/README.md
modified: modules/aws-anyscale-iam/README.md
new file: modules/aws-anyscale-iam/cluster_node-secretsmanager-getsecret-kms.tmpl
new file: modules/aws-anyscale-iam/cluster_node-secretsmanager-getsecret.tmpl
modified: modules/aws-anyscale-iam/iam-policies-data.tf
modified: modules/aws-anyscale-iam/main.tf
modified: modules/aws-anyscale-iam/test/anyscale-test/main.tf
modified: modules/aws-anyscale-iam/test/anyscale-test/outputs.tf
modified: modules/aws-anyscale-iam/variables.tf
modified: modules/aws-anyscale-s3-policy/README.md
modified: modules/aws-anyscale-s3-policy/examples/README.md
modified: modules/aws-anyscale-s3/README.md
modified: modules/aws-anyscale-securitygroups/README.md
modified: modules/aws-anyscale-vpc/README.md
new file: test/REQUIREMENTS.txt
new file: test/test_cloud_register_manual.py
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
📚 Documentation/Examples
[upd] aws-anyscale-iam: Add Optional SecretsManager IAM policy @brent-anyscale (#35)
This commit adds a new IAM policy for SecretsManager. This policy allows passing in a new parameter with a list of secrets - as well as a KMS key to use (optional). This policy is then assigned to the Cluster Node IAM role. This allows the cluster to read the secret which is then used for BYOD (Bring Your Own Docker) images that are in private, password protected repositories.
Additional updates include a new example named kitchensink (WIP), updates to the latest Terraform and AWS Provider versions. There are also updates to the unit tests with the plan to automate building the resources, deploying an Anyscale Cloud, using Functional Verification, and then destroying the resources as part of an automated github action (also a WIP).
On branch brent/iam-secrets
Changes to be committed:
modified: .tflint.hcl
modified: CHANGELOG.md
modified: README.md
deleted: examples/anyscale-v2-createendpoints/README.md
deleted: examples/anyscale-v2-createendpoints/main.tf
deleted: examples/anyscale-v2-createendpoints/outputs.tf
modified: examples/anyscale-v2-existing-vpc/main.tf
new file: examples/anyscale-v2-kitchensink/README.md
new file: examples/anyscale-v2-kitchensink/main.tf
new file: examples/anyscale-v2-kitchensink/outputs.tf
renamed: examples/anyscale-v2-createendpoints/variables.tf -> examples/anyscale-v2-kitchensink/variables.tf
renamed: examples/anyscale-v2-createendpoints/versions.tf -> examples/anyscale-v2-kitchensink/versions.tf
modified: main.tf
modified: modules/aws-anyscale-efs/README.md
modified: modules/aws-anyscale-iam/README.md
new file: modules/aws-anyscale-iam/cluster_node-secretsmanager-getsecret-kms.tmpl
new file: modules/aws-anyscale-iam/cluster_node-secretsmanager-getsecret.tmpl
modified: modules/aws-anyscale-iam/iam-policies-data.tf
modified: modules/aws-anyscale-iam/main.tf
modified: modules/aws-anyscale-iam/test/anyscale-test/main.tf
modified: modules/aws-anyscale-iam/test/anyscale-test/outputs.tf
modified: modules/aws-anyscale-iam/variables.tf
modified: modules/aws-anyscale-s3-policy/README.md
modified: modules/aws-anyscale-s3-policy/examples/README.md
modified: modules/aws-anyscale-s3/README.md
modified: modules/aws-anyscale-securitygroups/README.md
modified: modules/aws-anyscale-vpc/README.md
new file: test/REQUIREMENTS.txt
new file: test/test_cloud_register_manual.py
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