-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Feature Request] Support partial updates to database secret backend #3544
Comments
duplicate of #1468 |
Ran into this today. For instance, adding to Really frustrating. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request:
For some context, I have a repo which codifies most of the mount configuration in my system - basically roles and secret backend configuration (minus the secrets themselves). That means when someone needs a new secret backend, we'll have to manually mount + configure it. After that if we have to add additional roles or make configuration changes (e.g., change a default_lease_ttl) we can do so via mount tuning or via the secret backend's API.
Per the docs, if I want to set up a database connection via the database secret backend, I must issue a write like so:
vault write database/config/connection plugin_name="mysql-database-plugin" connection_url="user:pass@tcp(host:port)/db"
So for example, if I want to add
max_connection_lifetime=10m
to the connection, I have to issue this:vault write database/config/connection plugin_name="mysql-database-plugin" connection_url="user:pass@tcp(host:port)/db" max_connection_lifetime=10m
It would be nice to allow partial updates like this:
vault write database/config/connection max_connection_lifetime=10m
The text was updated successfully, but these errors were encountered: