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

Remove default TTLs for vault_gcp_secret_backend #426

Merged
merged 1 commit into from
Jun 3, 2019

Conversation

lawliet89
Copy link
Contributor

@lawliet89 lawliet89 commented May 27, 2019

The default in Vault API docs are "" which refers to the system TTL
settings. The resource should not attempt to set its own defaults, which
is going to be surprising for users

https://www.vaultproject.io/api/system/mounts.html#enable-secrets-engine

The default in Vault API docs are "0" which refers to the system TTL
settings. The resource should not attempt to set its own defaults, which
is going to be surprising for users
Copy link
Contributor

@tyrannosaurus-becks tyrannosaurus-becks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @lawliet89 ! Yes, I think this looks great. I see that if it's set to 0 it'll use the system default, which makes much more sense.

@tyrannosaurus-becks tyrannosaurus-becks merged commit 6d0eeb6 into hashicorp:master Jun 3, 2019
dandandy pushed a commit to dandandy/terraform-provider-vault that referenced this pull request Jun 17, 2021
Remove default TTLs for vault_gcp_secret_backend
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.

2 participants