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

Fix Stretch Private Cloud creation in vmwareengine #17875

Conversation

modular-magician
Copy link
Collaborator

This PR contains some resource refactoring and bug fixes based on the manual testing of Stretch PCs and is a continuation of #10340. These changes were manually tested by performing CRUD operations on a Stretch Private Cloud using terraform.

Please note that currently stretch private clouds need at least 6 nodes (for context, a majority of current vmareengine resource tests use a 1 node PC). Further, it is currently only supported in 3 regions, and all of them are full with customer nodes. Hence, it would not be possible to nightly run stretch PC tests on Terraform.

Release Note Template for Downstream PRs (will be copied)

vmwareengine: fixed stretched cluster creation in `google_vmwareengine_private_cloud`

Derived from GoogleCloudPlatform/magic-modules#10443

[upstream:71d5293f31bbbbd98a7e073050e4f52e092fa964]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 28e14fe into hashicorp:main Apr 16, 2024
2 checks passed
Copy link

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 May 18, 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