Releases: anyscale/terraform-google-anyscale-cloudfoundation-modules
v0.18.2
🐛 Bug Fixes
fix: re-add trivy to pre-commit hooks @brent-anyscale (#49)
While troubleshooting trivy, it was removed from the pre-commit hooks. This re-adds it with a note of known problems tied to specific versions of Trivy.
On branch brent/re-add-trivy
Changes to be committed:
modified: .pre-commit-config.yaml
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):
pre-commit update
Github Chores
fix: re-add trivy to pre-commit hooks @brent-anyscale (#49)
While troubleshooting trivy, it was removed from the pre-commit hooks. This re-adds it with a note of known problems tied to specific versions of Trivy.
On branch brent/re-add-trivy
Changes to be committed:
modified: .pre-commit-config.yaml
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):
pre-commit update
v0.18.1
🐛 Bug Fixes
When both an Existing VPC and an Existing Firewall were present in a project, the Anyscale firewall submodule would fail to execute and throw an error.
Added an additional example to demonstrate how to use an Existing VPC with an Existing Firewall.
Additional minor updates to wording for clarity in the README and other documentation files.
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
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):
Description
We want to be able to setup and manage [Network Endpoint Groups](https://cloud.google.com/load-balancing/docs/negs#:~:text=A%20network%20endpoint%20group%20(NEG,serverless%20workloads%2C%20and%20containerized%20workloads.). NEGs will soon replace instance group as the backend for backend services as they offer a bit more flexibility.
We don't currently ask for permission to manage NEGs and will need to add these perms as the default in order to enable the switch.
Does this introduce a breaking change?
- Yes
- No
v0.17.3
📚 Documentation/Examples
add: Example with no Filestore @brent-anyscale (#46)
Filestore for NFS mounts is no longer required. This PR includes an example configuration using these modules to deploy the resources necessary for an Anyscale Cloud without a Filestore resource.
Minimal Requirements
Anyscale CLI Version: anyscale-0.25.6
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):
New example
Does this introduce a breaking change?
- Yes
- No
v0.17.2
📚 Documentation/Examples
Cleanup variables & readme @brent-anyscale (#45)
Make it clear that the logging-sink configuration is to enable/disable a submodule. Additional updates to ensure that required variables show up at the top of the list of variables in the default README.
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.1
📚 Documentation/Examples
upd: README to fix references to examples and general cleanup @brent-anyscale (#44)
On branch brent/upd-root-readme
Changes to be committed:
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.17.0
upd: GKE Sub-Module with additional configuration options @brent-anyscale (#40)
On branch brent/gke-standard
Changes to be committed:
modified: ../README.md
modified: README.md
modified: main.tf
modified: variables.tf
modified: ../main.tf
modified: ../outputs.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):
WIP
Does this introduce a breaking change?
- Yes
- No
v0.16.3
🐛 Bug Fixes
This update adds the missing tiers for the Google Cloud Filestore module. The module now supports the following tiers: STANDARD
, PREMIUM
, BASIC_HDD
, BASIC_SSD
, HIGH_SCALE_SSD
, ENTERPRISE
, ZONAL
, and REGIONAL
.
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.16.2
🐛 Bug Fixes
fix: google-anyscale-iam: IAM SA Desc when passing in a CloudID @brent-anyscale (#42)
When passing in a Cloud ID, the IAM SA description tried to add var.google_region
, however, this variable was always null. This caused the IAM SA to fail to create.
Additional updates to pre-commit-config.yaml to update to the latest hook versions.
On branch brent/fix-iam-sa-desc
Changes to be committed:
modified: .pre-commit-config.yaml
modified: modules/google-anyscale-iam/README.md
new file: modules/google-anyscale-iam/data.tf
modified: modules/google-anyscale-iam/gke-sa.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
Fix link to GC deployment guide @kylegallatin (#41)
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.16.1
fix: E2E test - Additional sleeps for cloud resource deletion @brent-anyscale (#38)
Changes to be committed:
modified: test_cloud_register_manual.py
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