fix: Restrict maximum AzureRM provider version for bootstrap module #93
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
|
/idempotence paths="examples/dedicated_vmseries"
|
michalbil
approved these changes
Sep 13, 2024
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.
Description
This PR adds a new AzureRM provider version constraint that limits maximum provider version to
3.114in the bootstrap module (temporary solution) due to a provider bug.Motivation and Context
Our examples utilising bootstrap module currently are not idempotent with the newest AzureRM provider within v3 major branch. It's fixed in AzureRM provider v4 (which is going to be introduced in the next minor version release). Temporarily we need to restrict the maximum version before the bug was introduced.
How Has This Been Tested?
ChatOps
Types of changes
Checklist