Fix perma-diff in google_container_cluster
when cluster_dns_scope
is unspecified
#21637
+47
−15
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.
Terraform defaults this field to DNS_SCOPE_UNSPECIFIED, but the API
corrects this to an empty value.
Following https://googlecloudplatform.github.io/magic-modules/develop/diffs/#default_if_empty
to tackle this issue.
To make writing DNS tests faster, I refactored the helper function
testAccContainerCluster_autopilot_withDNSConfig
I added previously intotestAccContainerCluster_withAdvancedDNSConfig
.Fixes #20285
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.
Derived from GoogleCloudPlatform/magic-modules#13150