Conversation
ghost
force-pushed
the
backport/bugfix/issue-28274-providers-mirroring-honor-lockfile/legally-upright-mastiff
branch
from
7591ce8 to
1c7700f
Compare
Contributor
|
Proposing for 1.4.1. |
alisdair
deleted the
backport/bugfix/issue-28274-providers-mirroring-honor-lockfile/legally-upright-mastiff
branch
Contributor
|
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
Contributor
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Backport
This PR is auto-generated from #32742 to be assessed for backporting due to the inclusion of the label 1.4-backport.
The below text is copied from the body of the original PR.
When mirroring providers using
terraform providers mirrorcommand, AND, if dependency lock file exists, selected provider version might not match the dependency lock file.So, this PR addresses this issue by honouring the lock file if present.
A new e2e test case has been added to cover this new case.
Fixes #28274
Target Release
1.4.1
Draft CHANGELOG entry
BUG FIXES
terraform providers mirror: support dependency lock file