Use the path for data.vault_generic_secret ID #849
Merged
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.
Terraform 0.13.0 introduces the values for data sources to be read as part of the
plan
phase. Once a generic secret is written to state, future plan or applies will change the ID because it's using theRequestID
that read it as the ID. This is demonstrated in #847Here we change the data source to use the
path
attribute instead, which should remain unique. It's also unlikely that anyone would be usingdata.vault_generic_secret.name.id
as an input value, as it's a UUID from Vault that identifies that specific request that read the value and provides no actual value outside of that.Fixes #847