Apply maintenance policy updates after upgrades so validation on maintenance policy uses the new versions. #8922
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
…tenance policy uses the new versions. (#12569) [upstream:81de2e099caee29e40283e5eff4770d8ca90979c] Signed-off-by: Modular Magician <[email protected]>
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.
Switch the ordering of updates so maintenance policy updates get applied after upgrades. This means that validation on maintenance exclusions will use the new version as opposed to the old version which means you can upgrade to a new version and set an exclusion until end of support for the new version in one
terraform applycommand.Fixes hashicorp/terraform-provider-google#20556
Release note:
Derived from GoogleCloudPlatform/magic-modules#12569