fix: [dns] fix hash function for network_url in ManagedZone and Policy resources #6199
+301
−4
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 someone is trying to attach a private DNS zone to multiple networks in different projects, if the network name is the same across some of those projects, the resource will only attach only one of that networks with the same name, even if they are on different projects.
Example:
project1
with networksnetwork1
andnetwork2
to be attachedproject2
with networksnetwork2
andnetwork3
to be attachedThe Terraform resource will only try to attach
network1
fromproject1
,network2
andnetwork3
fromproject3
thus ignoringnetwork2
fromproject1
Updating the way how the resource is handling the hash will fix this issue.
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#8716