Skip to content

Releases: anyscale/terraform-google-anyscale-cloudfoundation-modules

v0.12.0

27 Mar 22:49
832aed3
Compare
Choose a tag to compare

🚀 Enhancements

feat: Update to TF GCP Provider v5 @brent-anyscale (#20)

This pull request updates the GCP Terraform Provider to version 5.

Additionally, updates have been made to the VPC Submodule and VPC Firewall Submodule to accommodate changes in the GCP APIs. Lastly, this includes a fix that ensures that changes to parameters passed into the root module do not trigger the recreation of unrelated resources.

BUG FIXES:

  • VPC Submodule
    • Proxy Subnet fix for change to GCP APIs related to IPv6 - GCP released a change and with v5 of the GCP Terraform Provider, the IPv6 parameter for Proxy Only Subnets is not suported/required.
    • Subnet Names are now managed by the root module
      • The previous behavior was causing the replacement of Subnets on any parameter change to the root module.
  • VPC Firewall Submodule
    • Update to use VPC ID for attachment instead of dynamically identifying from the name. - The previous behavior was causing the replacement of the VPC Firewall on any parameter change to the root module.

OTHER CHANGES:

  • Change from tfsec to trivy for pre-commit
  • TFLint updated for GCP Ruleset
  • General updates/fixes for all tests in submodule examples for VPC Firewall and CloudStorage
  • pre-commit updates to the latest revisions
On branch brent/vpc-proxysubnet-fix Changes to be committed:

modified: .pre-commit-config.yaml
modified: .tflint.hcl
modified: CHANGELOG.md
modified: README.md
modified: examples/anyscale-v2-commonname/README.md
modified: examples/anyscale-v2-commonname/main.tf
modified: examples/anyscale-v2-commonname/outputs.tf
modified: examples/anyscale-v2-commonname/versions.tf
modified: examples/anyscale-v2-existingidentityfederation/README.md
modified: examples/anyscale-v2-existingidentityfederation/versions.tf
modified: examples/anyscale-v2-existingproject/README.md
modified: examples/anyscale-v2-existingproject/versions.tf
modified: examples/anyscale-v2-kitchensink/README.md
modified: examples/anyscale-v2-kitchensink/versions.tf
modified: examples/anyscale-v2-privatenetwork/README.md
modified: examples/anyscale-v2-privatenetwork/versions.tf
modified: examples/anyscale-v2-vpc-shared/README.md
modified: examples/anyscale-v2-vpc-shared/versions.tf
modified: examples/anyscale-v2/README.md
modified: examples/anyscale-v2/versions.tf
modified: main.tf
modified: modules/google-anyscale-cloudapis/README.md
modified: modules/google-anyscale-cloudapis/examples/README.md
modified: modules/google-anyscale-cloudapis/examples/versions.tf
modified: modules/google-anyscale-cloudapis/main.tf
modified: modules/google-anyscale-cloudapis/variables.tf
modified: modules/google-anyscale-cloudapis/versions.tf
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/versions.tf
modified: modules/google-anyscale-cloudstorage/versions.tf
modified: modules/google-anyscale-filestore/README.md
modified: modules/google-anyscale-filestore/examples/README.md
modified: modules/google-anyscale-filestore/examples/versions.tf
modified: modules/google-anyscale-filestore/versions.tf
modified: modules/google-anyscale-iam/README.md
modified: modules/google-anyscale-iam/examples/README.md
modified: modules/google-anyscale-iam/examples/versions.tf
modified: modules/google-anyscale-iam/versions.tf
modified: modules/google-anyscale-memorystore/README.md
modified: modules/google-anyscale-memorystore/examples/README.md
modified: modules/google-anyscale-memorystore/examples/versions.tf
modified: modules/google-anyscale-memorystore/versions.tf
modified: modules/google-anyscale-project/README.md
modified: modules/google-anyscale-project/examples/README.md
modified: modules/google-anyscale-project/examples/versions.tf
modified: modules/google-anyscale-project/versions.tf
modified: modules/google-anyscale-vpc-firewall/README.md
deleted: modules/google-anyscale-vpc-firewall/data.tf
modified: modules/google-anyscale-vpc-firewall/examples/README.md
modified: modules/google-anyscale-vpc-firewall/examples/main.tf
modified: modules/google-anyscale-vpc-firewall/examples/versions.tf
modified: modules/google-anyscale-vpc-firewall/main.tf
modified: modules/google-anyscale-vpc-firewall/variables.tf
modified: modules/google-anyscale-vpc-firewall/versions.tf
modified: modules/google-anyscale-vpc/README.md
modified: modules/google-anyscale-vpc/examples/README.md
modified: modules/google-anyscale-vpc/examples/versions.tf
modified: modules/google-anyscale-vpc/main.tf
modified: modules/google-anyscale-vpc/private-subnet.tf
modified: modules/google-anyscale-vpc/proxy-subnet.tf
modified: modules/google-anyscale-vpc/public-subnet.tf
modified: modules/google-anyscale-vpc/versions.tf
modified: test/anyscale-v2-e2e-private-test/versions.tf
modified: test/anyscale-v2-e2e-public-test/versions.tf
modified: test/requirements.txt
modified: test/test_cloud_register_manual.py
modified: variables.tf
modified: 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):

v0.11.0

13 Feb 03:23
1174c44
Compare
Choose a tag to compare

🚀 Enhancements

feat: update cors rules in google-anyscale-cloudstorage module @brent-anyscale (#19)

With some upcoming changes to the front-end, Anyscale has additional
changes for the CORS rules for the Google Cloud Storage bucket.

On branch brent/update-cors
Changes to be committed:
modified: modules/google-anyscale-cloudstorage/README.md
modified: modules/google-anyscale-cloudstorage/variables.tf
modified: README.md
modified: test/anyscale-v2-e2e-public-test/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.10.0

14 Dec 20:44
60b1109
Compare
Choose a tag to compare

🚀 Enhancements

feat: Shared VPCs support, Minimal scoped IAM Role @brent-anyscale (#17)

BREAKING CHANGE

This commit introduces new features to support Shared VPCs on GCP. GCP Shared VPCs are a way to share a VPC network across multiple Projects. You can see an example of this in the anyscale-v2-vpc-shared example folder.

It also introduces a minimally scoped IAM Role for GCP to support Anyscale. With this change, the IAM submodule is refactored to better align with GCP names for IAM related resources. This change is a breaking change and should NOT be used to upgrade existing resources. It is recommended to create a new Anyscale Cloud and migrate your resources to the new Cloud.

There are additional fixes and improvements to the Firewall module, allowing traffic from the GCP Health Monitoring CIDR ranges.

Additional updates to pre-commit-config, tflint, and other cleanup to examples.

This update refactors the IAM submodule and should not be used for upgrading existing resources. IAM Service Accounts will be replaced which is not a supported entity to "edit" in an Anyscale Cloud. If you need to upgrade, please create a new Anyscale Cloud with these resources and then migrate your workloads between the clouds.

On branch brent/iam-minimalrole Changes to be committed: modified: .gitignore modified: .pre-commit-config.yaml modified: .tflint.hcl modified: CHANGELOG.md modified: README.md modified: data.tf modified: examples/anyscale-v2-commonname/README.md modified: examples/anyscale-v2-commonname/outputs.tf modified: examples/anyscale-v2-existingidentityfederation/README.md modified: examples/anyscale-v2-existingidentityfederation/main.tf modified: examples/anyscale-v2-existingidentityfederation/outputs.tf modified: examples/anyscale-v2-existingidentityfederation/variables.tf modified: examples/anyscale-v2-existingproject/README.md modified: examples/anyscale-v2-existingproject/outputs.tf modified: examples/anyscale-v2-kitchensink/main.tf modified: examples/anyscale-v2-kitchensink/outputs.tf modified: examples/anyscale-v2-privatenetwork/README.md modified: examples/anyscale-v2-privatenetwork/main.tf modified: examples/anyscale-v2-privatenetwork/outputs.tf new file: examples/anyscale-v2-vpc-shared/README.md new file: examples/anyscale-v2-vpc-shared/main.tf new file: examples/anyscale-v2-vpc-shared/outputs.tf new file: examples/anyscale-v2-vpc-shared/variables.tf new file: examples/anyscale-v2-vpc-shared/versions.tf modified: examples/anyscale-v2/README.md modified: examples/anyscale-v2/outputs.tf modified: main.tf modified: modules/google-anyscale-cloudapis/README.md modified: modules/google-anyscale-cloudapis/examples/README.md modified: modules/google-anyscale-cloudapis/examples/variables.tf modified: modules/google-anyscale-cloudapis/variables.tf modified: modules/google-anyscale-cloudstorage/README.md modified: modules/google-anyscale-cloudstorage/variables.tf modified: modules/google-anyscale-filestore/README.md modified: modules/google-anyscale-iam/README.md modified: modules/google-anyscale-iam/examples/README.md modified: modules/google-anyscale-iam/examples/main.tf modified: modules/google-anyscale-iam/examples/outputs.tf modified: modules/google-anyscale-iam/examples/variables.tf modified: modules/google-anyscale-iam/main.tf modified: modules/google-anyscale-iam/outputs.tf new file: modules/google-anyscale-iam/roles.tf modified: modules/google-anyscale-iam/variables.tf modified: modules/google-anyscale-memorystore/README.md modified: modules/google-anyscale-memorystore/variables.tf modified: modules/google-anyscale-project/README.md modified: modules/google-anyscale-project/variables.tf modified: modules/google-anyscale-vpc-firewall/README.md modified: modules/google-anyscale-vpc-firewall/examples/README.md modified: modules/google-anyscale-vpc-firewall/examples/variables.tf modified: modules/google-anyscale-vpc-firewall/main.tf modified: modules/google-anyscale-vpc-firewall/variables.tf modified: modules/google-anyscale-vpc/README.md modified: modules/google-anyscale-vpc/examples/README.md modified: modules/google-anyscale-vpc/examples/variables.tf modified: modules/google-anyscale-vpc/proxy-subnet.tf modified: modules/google-anyscale-vpc/variables.tf modified: outputs.tf modified: test/anyscale-v2-e2e-private-test/outputs.tf modified: test/anyscale-v2-e2e-public-test/outputs.tf modified: 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

v0.9.0

26 Sep 16:36
0b5abb6
Compare
Choose a tag to compare

🚀 Enhancements

feat: Add support for existing identity federation @brent-anyscale (#16)

This commit adds support for existing Workload Identity Federation. This is done by adding a new variable to the module, existing_workload_identity_provider_name and some additional changes to the IAM submodule.

A new example has also been provided to demonstrate the usage of this new feature. Please be aware that you are responsible for creating the Workload Identity Federation pool and provider if using this new example. You can read more about those requirements in the Anyscale Documentation.

Additional updates include:

  • Update to E2E test
On branch brent/iam-identityfederation-upd Changes to be committed: modified: CHANGELOG.md modified: README.md new file: examples/anyscale-v2-existingidentityfederation/README.md new file: examples/anyscale-v2-existingidentityfederation/main.tf new file: examples/anyscale-v2-existingidentityfederation/outputs.tf new file: examples/anyscale-v2-existingidentityfederation/variables.tf new file: examples/anyscale-v2-existingidentityfederation/versions.tf modified: main.tf modified: modules/google-anyscale-iam/README.md modified: modules/google-anyscale-iam/examples/README.md modified: modules/google-anyscale-iam/examples/main.tf modified: modules/google-anyscale-iam/examples/variables.tf modified: modules/google-anyscale-iam/main.tf modified: modules/google-anyscale-iam/variables.tf modified: 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

v0.8.2

20 Sep 22:28
3e6a4ac
Compare
Choose a tag to compare

🐛 Bug Fixes

[fix] Add Proxy Subnets to VPC Module for Private Networking @brent-anyscale (#15)

This PR introduces the ability to create a proxy subnet within the VPC submodule, tailored for load balancers, further enhancing Anyscale Services' compatibility with private networking on GCP.

Additionaly updates include cleanup to the README files, variable cleanup with better descriptions, and output cleanup in the examples.

We've made some preliminary updates to our end-to-end tests. Kindly note, this area remains a work in progress and further refinements will follow.

On branch brent/privatevpc-proxysubnet Changes to be committed: modified: .pre-commit-config.yaml modified: CHANGELOG.md modified: README.md modified: examples/anyscale-v2-commonname/main.tf modified: examples/anyscale-v2-commonname/outputs.tf modified: examples/anyscale-v2-existingproject/outputs.tf modified: examples/anyscale-v2-privatenetwork/main.tf modified: examples/anyscale-v2-privatenetwork/outputs.tf modified: examples/anyscale-v2/outputs.tf modified: main.tf modified: modules/google-anyscale-filestore/README.md modified: modules/google-anyscale-filestore/variables.tf modified: modules/google-anyscale-vpc-firewall/README.md modified: modules/google-anyscale-vpc-firewall/main.tf modified: modules/google-anyscale-vpc-firewall/variables.tf modified: modules/google-anyscale-vpc/README.md new file: modules/google-anyscale-vpc/proxy-subnet.tf modified: modules/google-anyscale-vpc/variables.tf modified: 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

v0.8.1

19 Sep 22:51
dcddcdd
Compare
Choose a tag to compare

🐛 Bug Fixes

[fix] google-anyscale-iam - fix descriptions when cloud_id provided @brent-anyscale (#14)

When the anyscale_cloud_id variable is provided, the description was looking for a variable that isn't sent to the module. This unblocks this situation - however a more complete will follow and fix to add the missing variable to the module.

On branch brent/iambugfix Changes to be committed: modified: CHANGELOG.md modified: modules/google-anyscale-iam/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.8.0

15 Sep 14:23
28e5ab7
Compare
Choose a tag to compare

Support for Anyscale Service Head Node Fault Tolerance

This release adds a new optional submodule google-anyscale-memorystore which can be used to create a Memorystore Redis instance which is then used with Anyscale Services to enable head node fault tolerance. It includes the following additional updates:

  • Updates to google-anyscale-cloudapis to optionally enable memorystore api (redis.googleapis.com)
  • Example updates including new kitchensink example
  • Root module updates to support optional new google-anyscale-memorystore module

To see how this module can be enabled and used, please look in the examples/anyscale-v2-kitchensink or the anyscale-v2-privatenetwork folders

Support for GCP Logging and Cloud Monitoring

Additional updates to support via Vector for logging integration with GCP Logging and Cloud Monitoring

  • Updates to google-anyscale-iam to optionally grant access to GCP Logging and Cloud Monitoring
  • Updates to google-anyscale-cloudapis to optionally enable GCP Logging (logging.googleapis.com) and Cloud Monitoring (monitoring.googleapis.com)

Additional updates:

  • General doc updates and cleanup
  • Root module variables cleanup with better descriptions and examples
  • tflint and changelog updates
  • Initial pass at End to End testing integration
On branch brent/memorystore Changes to be committed: modified: .pre-commit-config.yaml modified: .tflint.hcl modified: CHANGELOG.md modified: README.md modified: examples/anyscale-v2-kitchensink/README.md new file: examples/anyscale-v2-kitchensink/main.tf new file: examples/anyscale-v2-kitchensink/outputs.tf new file: examples/anyscale-v2-kitchensink/variables.tf new file: examples/anyscale-v2-kitchensink/versions.tf modified: examples/anyscale-v2-privatenetwork/README.md modified: examples/anyscale-v2-privatenetwork/main.tf modified: examples/anyscale-v2-privatenetwork/outputs.tf modified: main.tf modified: modules/google-anyscale-cloudapis/README.md modified: modules/google-anyscale-cloudapis/examples/main.tf modified: modules/google-anyscale-cloudapis/main.tf modified: modules/google-anyscale-cloudapis/outputs.tf 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-iam/examples/main.tf modified: modules/google-anyscale-iam/main.tf modified: modules/google-anyscale-iam/variables.tf new file: modules/google-anyscale-memorystore/README.md new file: modules/google-anyscale-memorystore/data.tf new file: modules/google-anyscale-memorystore/examples/README.md new file: modules/google-anyscale-memorystore/examples/main.tf new file: modules/google-anyscale-memorystore/examples/outputs.tf new file: modules/google-anyscale-memorystore/examples/variables.tf new file: modules/google-anyscale-memorystore/examples/versions.tf new file: modules/google-anyscale-memorystore/main.tf new file: modules/google-anyscale-memorystore/outputs.tf new file: modules/google-anyscale-memorystore/variables.tf new file: modules/google-anyscale-memorystore/versions.tf modified: modules/google-anyscale-project/README.md modified: modules/google-anyscale-project/main.tf modified: modules/google-anyscale-vpc-firewall/README.md modified: modules/google-anyscale-vpc/README.md modified: outputs.tf new file: test/requirements.txt new file: test/test_cloud_register_manual.py modified: variables.tf

v0.7.1

15 Aug 16:52
964f13d
Compare
Choose a tag to compare

📚 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

07 Jul 20:50
aa33bcb
Compare
Choose a tag to compare

🚀 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

06 Jul 21:08
010c1a1
Compare
Choose a tag to compare

📚 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