PSS: Add savedStateStore
method to Meta
#37558
Open
+234
−2
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.
Description
This PR adds a new
savedStateStore
method that's similar to the existingsavedBackend
method onMeta
.The
savedBackend
method on Meta returns a backend that's configured using the backend state file's contents and isn't influenced by the current config. This method is used during state migration events ininit
commands, where Terraform needs to have an instance of the old backend, configured the old way, in order to access state to migrate to the new backend's location.Note: There is a variant called
backendFromState
that does a similar job but isn't considered in this PR. This variant is specific to users running init commands with-backend=false
as a flag.This PR adds a new
savedStateStore
method that's similar to the existingsavedBackend
method onMeta
. The method uses only backend state file data to configure and return a backend.Backend instance made using a provider that implements pluggable state storage.Target Release
N/A
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry