google_container_cluster: add Node auto-provisioning locations #7849
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[upstream:6333dff9a7be978d28fa026dd57c4fdd5c859fa7] Signed-off-by: Modular Magician <[email protected]>
modular-magician
deleted the
downstream-pr-6333dff9a7be978d28fa026dd57c4fdd5c859fa7
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Node auto-provisioning is enabled, the terraform provider currently cannot be used to define node auto-provisioning locations. This configuration is, as of today, presently limited to the UI, gcloud, or API.
Tests for google_container_cluster were already successfully executed locally
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#11305