website: Document TF_PLUGIN_CACHE_MAY_BREAK_DEPENDENCY_LOCK_FILE env var #32765
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.
This is an alternative way to set the CLI configuration setting plugin_cache_may_break_dependency_lock_file to activate the transitional compatibility behavior that prefers to break the dependency lock file if that would create an additional opportunity to use the plugin cache.
This has been supported since #32726 but I forgot to update this particular doc section when I implemented it, despite @alisdair's attempt to prompt me which apparently I was too absent-minded to think about that day. 😖
While here I also fixed a minor bug from #32494 (where this doc section originated) where the heading was at the wrong nesting level and so would've messed up the navigation tree as previously defined. The heading is now nested under "Provider Installation" as originally intended.