Update google_dns_managed_zone.private_visibility_config
to require at least one of gke_clusters
or networks
#15443
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.
#15428
With cluster-scoped dns zones (https://cloud.google.com/dns/docs/zones/configure-scopes), you can now specify a zone that applies just to a gke cluster, without applying to the entire network. This change removes the
required
attribute ofprivate_visibility_config.networks
field and setsat_least_one_of
on theprivate_visibility_config
to allow for one or both ofgke_clusters
ornetworks
.gcloud
output confirms this:If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
in the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#8581