terraform: Compare locks and provider requirements #26761
Merged
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
alisdair
added
cli
0.14-backport
This comment has been minimized.
This comment has been minimized.
|
The above comment was a misread of test output. I'll investigate these test failures and re-request review if I can address them. |
alisdair
force-pushed
the
alisdair/compare-locks-and-provider-requirements
branch
2 times, most recently
from
019a64c
to
184c006
Compare
Codecov Report
|
alisdair
force-pushed
the
alisdair/compare-locks-and-provider-requirements
branch
2 times, most recently
from
b603e2b
to
60353da
Compare
pselle
reviewed
Nov 5, 2020
| } | ||
| opts.LockedDependencies = lockedDependencies | ||
|
|
||
| // If any unmanaged providers or dev overrides are enabled, they must |
alisdair
force-pushed
the
alisdair/compare-locks-and-provider-requirements
branch
from
60353da
to
0970f83
Compare
pselle
approved these changes
Nov 5, 2020
When building a context, we read the dependency locks and ensure that the provider requirements from the configuration can be satisfied. If the configured requirements change such that the locks need to be updated, we explain this and recommend running "terraform init". This check is ignored for any providers which are locally marked as in development. This includes unmanaged providers and those listed in the provider installation `dev_overrides` block.
alisdair
force-pushed
the
alisdair/compare-locks-and-provider-requirements
branch
from
0970f83
to
10cc25f
Compare
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When building a context, we read the dependency locks and ensure that the provider requirements from the configuration can be satisfied. If the configured requirements change such that the locks need to be updated, we explain this and recommend running "terraform init".
This check is ignored for any providers which are locally marked as in development. This includes unmanaged providers and those listed in the provider installation
dev_overridesblock.Fixes #26565.
Screenshot