accesscontextmanager - Fix permadiff for perimeter ingress / egress rule resources #8526
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
…ule resources (#12119) Co-authored-by: Charlesleonius <charlesleon@google.com> [upstream:551f48015dbed65b65a5610cbb41b02f7f801bc6] Signed-off-by: Modular Magician <magic-modules@google.com>
modular-magician
deleted the
downstream-pr-551f48015dbed65b65a5610cbb41b02f7f801bc6
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.
Add diff suppress and custom flatten to fix permadiffs for changing resource orders on the api side. Sometimes the api returns a different order for (ingressTo|egressTo).resources. This change sorts the users config and the api response to always be in the same order to prevent diffs.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.
Derived from GoogleCloudPlatform/magic-modules#12119