v0.37.0

update cors_rules in docs @hongchaodeng (#89)

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.36.2

📚 Documentation/Examples

Change default value of attach_policy to false in the description @jpatra72 (#87)

default is false, but description says otherwise.

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.36.1

📚 Documentation/Examples

Remove --functional-verify flag from cloud register command outputs @hongchaodeng (#88)

The cloud resources on the Anyscale side aren't ready in the timeframe between registration and verification.

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.36.0

• No changes

v0.35.0

🚀 Enhancements

add: Update Security Group conf to allow either CIDR or Existing Security Group Configurations @brent-anyscale (#75)

This change allows for the use of either CIDR or Existing Security Group configurations for the security group ingress rules. This is useful for customers who have existing security groups they want to use to grant access to the Anyscale data plane.

This also cleans up commented-out code from older releases.

On branch brent/update-security-group-config
Changes to be committed:

• modified: CHANGELOG.md
• modified: README.md
• modified: main.tf
• modified: modules/aws-anyscale-securitygroups/examples/main.tf
• modified: modules/aws-anyscale-securitygroups/examples/outputs.tf
• modified: modules/aws-anyscale-securitygroups/main.tf
• modified: modules/aws-anyscale-securitygroups/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

📚 Documentation/Examples

add: Update Security Group conf to allow either CIDR or Existing Security Group Configurations @brent-anyscale (#75)

This change allows for the use of either CIDR or Existing Security Group configurations for the security group ingress rules. This is useful for customers who have existing security groups they want to use to grant access to the Anyscale data plane.

This also cleans up commented-out code from older releases.

On branch brent/update-security-group-config
Changes to be committed:

• modified: CHANGELOG.md
• modified: README.md
• modified: main.tf
• modified: modules/aws-anyscale-securitygroups/examples/main.tf
• modified: modules/aws-anyscale-securitygroups/examples/outputs.tf
• modified: modules/aws-anyscale-securitygroups/main.tf
• modified: modules/aws-anyscale-securitygroups/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.34.3

📚 Documentation/Examples

fix: replaced general_prefix with common_prefix in README.md @phachey-aurorasolar (#81)

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

Github Chores

fix: variables documentation, codeowners, and issue templates @brent-anyscale (#85)

• Update the variables.tf file to properly call out common_prefix - this was mentioned in the descriptions of multiple variables as general_prefix which was incorrect.
• Update the CODEOWNERS file to include the anyscale/public-terraform-owners team.
• Update the issue templates to include the anyscale/public-terraform-owners team.

On branch brent/gh-codeowner
Changes to be committed:

• modified: .github/CODEOWNERS
• modified: .github/ISSUE_TEMPLATE/bug-report.yml
• modified: .github/ISSUE_TEMPLATE/feature-request.yml
• modified: .github/ISSUE_TEMPLATE/security-issue.yml
• 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):
  Github codeowners, issues updates

Does this introduce a breaking change?

• Yes
• No

v0.34.2

📚 Documentation/Examples

upd: Cloud Resource example outputs @brent-anyscale (#82)

The new examples for registering resources for multi-resource clouds did not include the new external-id value. That has been added.

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.34.1

📚 Documentation/Examples

fix command to create a cloud resource @domcatalano (#79)

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.34.0

🚀 Enhancements

adding cloud resource yaml output and fix iam policy comma @domcatalano (#78)

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

adding cloud resource yaml output and fix iam policy comma @domcatalano (#78)

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.29.1

FEATURES:

• Removed null provider and updated validation of required variables to variables.tf
• Added additional IAM policies for CloudKeeper deployments of Anyscale Services
  • Anyscale Services v2 originally managed the deployment and load balancers via Cloudformation. This had inherrent limitations.
  • Anyscale Services will now be fully managed via the Control Plane via AWS APIs. This requires small adjustments to the IAM policies in use.
  • A future version will remove the Cloudformation IAM policies.

BUG FIXES:

• When passing in an organization id as well as the external id, if a cloud ID was also provided, it would not prioritize the correct local value for the external ID.
• The privatesubnets example was updated to use the external id, but did not also include the Organization ID. Both are now included.
• fix: IAM - Remove constraint on SetRulePriorities for ELBs
• fix: IAM - Cleaning up ACM Certificates was failing due to tagging constraint. Modified.

NOTES:

• Cleanup of unused IAM Roles for EKS Clusters
  • Removed the unused IAM roles TF files for EKS related resources from the IAM sub-module. These were originally created before Anyscale refactored the kubernetes examples to use AWS provided modules.
  • There are no functional differences for the VM stack resources.