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

On branch brent/example-no_filestore Changes to be committed: modified: CHANGELOG.md modified: README.md new file: examples/anyscale-v2-no_filestore/README.md new file: examples/anyscale-v2-no_filestore/main.tf new file: examples/anyscale-v2-no_filestore/outputs.tf new file: examples/anyscale-v2-no_filestore/variables.tf new file: examples/anyscale-v2-no_filestore/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):
  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

upd: Add additional Filestore tiers @brent-anyscale (#43)

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.

On branch brent/update-filestore-types Changes to be committed: modified: CHANGELOG.md modified: README.md modified: modules/google-anyscale-filestore/README.md 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):

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

v0.16.0

🚀 Enhancements

fix: Firewall port assignment was not correct @brent-anyscale (#37)
upd: CloudStorage to a member instead of binding for IAM policies. Changed from bucket_iam_member_override_roles to bucket_iam_member_additional_roles

Firewall Port Assignments were not correctly getting pulled in.

Changes to be committed:
modified: .pre-commit-config.yaml
modified: README.md
modified: main.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/main.tf
deleted: modules/google-anyscale-cloudstorage/test/README.md
deleted: modules/google-anyscale-cloudstorage/test/terraform_google_anyscale_cloudstorage_test.go
modified: modules/google-anyscale-cloudstorage/variables.tf
deleted: modules/google-anyscale-project/test/README.md
deleted: modules/google-anyscale-project/test/terraform_google_anyscale_project_test.go
modified: modules/google-anyscale-vpc-firewall/main.tf
deleted: modules/google-anyscale-vpc/test/terraform_google_anyscale_vpc_test.go
new file: test/anyscale-service/socket_test.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

fix: Firewall port assignment was not correct @brent-anyscale (#37)

Firewall Port Assignments were not properly getting pulled in, leaving all TCP Ports open.

upd: CloudStorage to a member instead of binding for IAM policies. Changed from bucket_iam_member_override_roles to bucket_iam_member_additional_roles

Changes to be committed:
modified: .pre-commit-config.yaml
modified: README.md
modified: main.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/main.tf
deleted: modules/google-anyscale-cloudstorage/test/README.md
deleted: modules/google-anyscale-cloudstorage/test/terraform_google_anyscale_cloudstorage_test.go
modified: modules/google-anyscale-cloudstorage/variables.tf
deleted: modules/google-anyscale-project/test/README.md
deleted: modules/google-anyscale-project/test/terraform_google_anyscale_project_test.go
modified: modules/google-anyscale-vpc-firewall/main.tf
deleted: modules/google-anyscale-vpc/test/terraform_google_anyscale_vpc_test.go
new file: test/anyscale-service/socket_test.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.15.3

🐛 Bug Fixes

fix: google-anyscale-vpc-firewall - Firewall Rule Names @brent-anyscale (#36)

The firewall rule names were not properly getting pulled from the variable when pulling from the predefined_firewall_rules.

Additonal updates:

• E2E test added for Services where functional verification isn't possible
• Removed the unit test for the firewall as it was no longer maintained.

Changes to be committed:
modified: ../modules/google-anyscale-vpc-firewall/main.tf
deleted: ../modules/google-anyscale-vpc-firewall/test/terraform_google_anyscale_vpc_firewall_test.go
new file: anyscale-service/service.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

v0.15.2

🐛 Bug Fixes

upd: google-anyscale-iam - Provide additional outputs and roles for K8s deployments @brent-anyscale (#35)

The new Anyscale K8s Operator has additional permission requirements which have been added to this.

Additional changes to support memberoutputs for IAM Service Accounts.

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

Github Chores

upd: google-anyscale-iam - Provide additional outputs and roles for K8s deployments @brent-anyscale (#35)

The new Anyscale K8s Operator has additional permission requirements which have been added to this.

Additional changes to support memberoutputs for IAM Service Accounts.

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