Exact Terraform provider versions in bundles #2579
Merged
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.
Resolves #2578
What is being addressed
Sometimes we use an approximate version of a provider (like ~>1.2.3) in bundles but that can break it when the next minor version is released. So when 1.2.4 will be released the bundle couldn't be installed.
The reason for this issue is that
terraform providers mirror
doesn't respect the lockfile - it will download the most recent version that respects therequired_provider
constraint (1.2.4 in the example), however the runtime will try to use the one from the lockfile (1.2.3)This is a known issue in Terraform
How is this addressed