v0.7.1

📚 Documentation/Examples

[upd] Documentation update with latest Terraform and Google Provider @brent-anyscale (#12)

Tested with Terraform 1.5.5 and Google Provider 4.78.0 Updates to pre-commit-config versions as well.

Changes to be committed:
modified: .pre-commit-config.yaml
modified: CHANGELOG.md
modified: README.md
modified: examples/anyscale-v2-existingproject/README.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc/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.7.0

🚀 Enhancements

[upd] google-anyscale-filestore submodule - change default tier/size @brent-anyscale (#11)

This commit updates the default tier and size for the filestore. It matches the defaults used in anyscale cloud setup. The default tier is now STANDARD and the default size is now 1024GB.

This also required changing the default location from region to availability zone. Because not all regions have a default AZ-A, the default location is now set to the region and AZ-B.

On branch brent/filestore-defaults
Changes to be committed:
modified: CHANGELOG.md
modified: README.md
modified: examples/anyscale-v2-commonname/main.tf
modified: examples/anyscale-v2-existingproject/main.tf
new file: examples/anyscale-v2-kitchensink/README.md
modified: main.tf
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-filestore/main.tf
modified: modules/google-anyscale-filestore/variables.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): changing Filestore defaults

Does this introduce a breaking change?

• Yes
• No

v0.6.1

📚 Documentation/Examples

[add] e2e tests for automated testing of the module @brent-anyscale (#10)

This adds two e2e tests for the module. One for public and one for private networking. The tests are used by the product team to validate both module changes and product changes.

On branch brent/e2e-tests
Changes to be committed:
modified: .github/create-release.yml
modified: README.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc/README.md
new file: test/anyscale-v2-e2e-private-test/main.tf
new file: test/anyscale-v2-e2e-private-test/outputs.tf
new file: test/anyscale-v2-e2e-private-test/variables.tf
new file: test/anyscale-v2-e2e-private-test/versions.tf
new file: test/anyscale-v2-e2e-public-test/main.tf
new file: test/anyscale-v2-e2e-public-test/outputs.tf
new file: test/anyscale-v2-e2e-public-test/variables.tf
new file: test/anyscale-v2-e2e-public-test/versions.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): Unit end to end tests.

Does this introduce a breaking change?

• Yes
• No

Github Chores

[add] e2e tests for automated testing of the module @brent-anyscale (#10)

This adds two e2e tests for the module. One for public and one for private networking. The tests are used by the product team to validate both module changes and product changes.

On branch brent/e2e-tests
Changes to be committed:
modified: .github/create-release.yml
modified: README.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc/README.md
new file: test/anyscale-v2-e2e-private-test/main.tf
new file: test/anyscale-v2-e2e-private-test/outputs.tf
new file: test/anyscale-v2-e2e-private-test/variables.tf
new file: test/anyscale-v2-e2e-private-test/versions.tf
new file: test/anyscale-v2-e2e-public-test/main.tf
new file: test/anyscale-v2-e2e-public-test/outputs.tf
new file: test/anyscale-v2-e2e-public-test/variables.tf
new file: test/anyscale-v2-e2e-public-test/versions.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): Unit end to end tests.

Does this introduce a breaking change?

• Yes
• No

v0.6.0

🚀 Enhancements

[upd] Root Module - Filestore Capacity default size @brent-anyscale (#9)

This matches the anyscale cloud setup Filestore default size. It also updates the description for the variable to be clearer on Google provider requirements.

On branch release-0.5.1
Changes to be committed:
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

📚 Documentation/Examples

[upd] Root Module - Filestore Capacity default size @brent-anyscale (#9)

This matches the anyscale cloud setup Filestore default size. It also updates the description for the variable to be clearer on Google provider requirements.

On branch release-0.5.1
Changes to be committed:
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.5.0

📚 Refactoring

[upd] Cloud APIs sub-module - add additional APIs @brent-anyscale (#8)

In reviewing the APIs that are enabled via the terraform, the product team suggested adding the following APIs to the list of enabled APIs:

• cloudresourcemanager.googleapis.com
• serviceusage.googleapis.com
• deploymentmanager.googleapis.com

This matches the APIs that are enabled via cloud setup - while not required for Terraform and Anyscale to work, this would cause errors with cloud verify if the APIs are not enabled.

Additional updates to readme's and validated with latest Terraform/Google providers.

On branch release-0.5.0
Changes to be committed:
modified: README.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudapis/variables.tf
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc/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.4.0

🚀 Enhancements

[upd] google-anyscale-cloudapis - add certificatemanager api @brent-anyscale (#7)

The certificatemanager api is utilized by Anyscale Services v2.

On branch release-0.4.0
Changes to be committed:
modified: CHANGELOG.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudapis/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.3.0

🚀 Enhancements

Release 0.3.0 @brent-anyscale (#6)

The STS api is not required for Anyscale to function. When you create the roles on the project, you can use the roles/iam.serviceAccountTokenCreator and that will allow the Anyscale service account to create tokens for itself. When doing this from the Google Cloud Console, it automatically enables the STS API, but it is not required.

On branch release-0.3.0
Changes to be committed:
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudapis/variables.tf
modified: CHANGELOG.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.2.3

📚 Documentation/Examples

[upd] examples and getting-started @brent-anyscale (#5)

Examples Updates

• The commonname and existingproject examples were updated. This removes the need to provide the anyscale_deploy_env as a required variable (it now has a default of production).
• These examples also now call out the ability to override the bucket location. This is noted in main.tf where you can set the variable anyscale_bucket_location
• The commonname readme also notes the requirement for having billing related permissions as it creates a project.

getting-started.md

• Updates to fix broken links
• General cleanup

On branch release-0.2.3
Changes to be committed:
modified: CHANGELOG.md
modified: examples/anyscale-v2-commonname/README.md
modified: examples/anyscale-v2-commonname/main.tf
modified: examples/anyscale-v2-commonname/variables.tf
modified: examples/anyscale-v2-existingproject/README.md
modified: examples/anyscale-v2-existingproject/main.tf
modified: examples/anyscale-v2-existingproject/variables.tf
modified: examples/anyscale-v2-privatenetwork/main.tf
modified: getting-started.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):
  Examples updates

v0.2.2

📚 Documentation/Examples

Examples variable name changes, added getting-started.md @brent-anyscale (#4)

examples/anyscale-v2 & anyscale-v2-commonname:
Update the variable names to better describe the resources needed from Google Cloud.

Added getting-started.md:
This file is a quick start guide to using the module, terraform, and Google Cloud.

google-anyscale-cloudstorage/examples:
Kitchen sink example was missing a variable required in the iam module.

README updates across all modules with updates to GCP provider version.

Changes to be committed:
modified: README.md
modified: examples/anyscale-v2-commonname/README.md
modified: examples/anyscale-v2-commonname/main.tf
modified: examples/anyscale-v2-commonname/variables.tf
modified: examples/anyscale-v2/README.md
modified: examples/anyscale-v2/main.tf
modified: examples/anyscale-v2/variables.tf
new file: getting-started.md
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-cloudstorage/examples/README.md
modified: modules/google-anyscale-cloudstorage/examples/main.tf
modified: modules/google-anyscale-cloudstorage/examples/variables.tf
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-vpc-firewall/README.md
modified: modules/google-anyscale-vpc/README.md

v0.2.1

🐛 Bug Fixes

[fix] google-anyscale-iam - Update project access from binding to member @brent-anyscale (#3)

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

google-anyscale-iam module:
The service account access for the project is now a member instead of a binding. This is to allow for situations where the binding would override access for other accounts.

On branch release-0.2.1
Changes to be committed:
modified: CHANGELOG.md
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-iam/main.tf

Does this introduce a breaking change?

• Yes
• No