fix: Restrict maximum AzureRM provider version for bootstrap module #36
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 limit maximum provider version to
3.95
in thebootstrap
module (temporary solution).Motivation and Context
Our examples utilising
bootstrap
module currently don't work with the newest AzureRM provider version (this is observed since version3.96
). On HashiCorp side, it seems that they addressed this issue but the fix hasn't been released yet.Once the problem is fixed on the HashiCorp side, we will switch to the newest AzureRM provider version.
How Has This Been Tested?
Types of changes
Checklist