Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update AlloyDB e2e tests and remove custom code for Public-IP feature #18344

Conversation

modular-magician
Copy link
Collaborator

Removes the custom code that was in place for the Public-IP feature now that the API supports creating instances with public IP enabled. Users shouldn't see a change in the behavior on TF side - though on the API side we are now enforcing the user to have a complex password to enable public IP. I've also updated the AlloyDB e2e tests relating to the Public-IP feature since they were breaking for the past couple of days from the API change.

Release Note Template for Downstream PRs (will be copied)

alloydb: created the resource `google_alloydb_instance` directly with public IP enabled instead of creating the resource with public IP disabled and then enabling it

Derived from GoogleCloudPlatform/magic-modules#10885

…hashicorp#10885)

[upstream:9d4ef4860a8d1988cd2207e276a020c6508238da]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 2c6c5ab into hashicorp:main Jun 6, 2024
4 checks passed
Copy link

github-actions bot commented Jul 7, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant