Backport of Ignore existing package hashes for providers lock
command into v1.2
#31478
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 #31389 to be assessed for backporting due to the inclusion of the label 1.2-backport.
The below text is copied from the body of the original PR.
This PR addresses part of the concerns raised in #29958
First, the
terraform providers lock
command will now ignore any existing hashes in the.terraform.lock.hcl
file. It will retrieve new hashes as if there were none already logged and then merge any new hashes into the existing list. There is now no validation of any existing hashes. It does this with the introduction of theInstallNewProvidersForce
InstallMode
, which is set withinproviders_lock.go
.Second, the output of the
terraform providers lock
has been made more verbose. There are three cases tracked for each (provider,platform) pair requested:Full example output: