Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the path for data.vault_generic_secret ID #849

Merged
merged 1 commit into from
Aug 21, 2020
Merged

Use the path for data.vault_generic_secret ID #849

merged 1 commit into from
Aug 21, 2020

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Aug 21, 2020

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 the RequestID that read it as the ID. This is demonstrated in #847

Here we change the data source to use the path attribute instead, which should remain unique. It's also unlikely that anyone would be using data.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

@ghost ghost added the size/XS label Aug 21, 2020
@kalafut kalafut requested a review from calvn August 21, 2020 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

data.vault_generic_secret id gets updated every run with terraform 0.13 and vault 2.12.2 provider
3 participants