-
Notifications
You must be signed in to change notification settings - Fork 375
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
database secrets engine needs documentation & design alignment #453
Comments
Are there any examples for doing the equivalent of this in the meantime? I am not clear how to do this https://www.vaultproject.io/docs/secrets/databases/mssql
|
Hey @jeffwecan, is there any update on this? I want to use the database secrets engine with HVAC. Could you provide some documentation for this? |
@Vishesh-Gupta Sorry, this sort of expanded documentation is still outstanding. I'm looking into some general maintenance and cutting a new release over the next week or so and I'll try to revisit this issue as part of that though! |
@jeffwecan I'd be happy to help on different parts of HVAC since I extensively use and work with Vault at my work. Let me know if you need help and I'd be happy to talk about it |
@Vishesh-Gupta: Great! If you're interested in helping with some of this repository's maintenance beyond general documentation / code contributions, feel free to shoot me an email at [email protected] and we can chat about it more. 😄 |
Hope this helps for Database secret engine doc. For Database Secret Engine - Dynamic SecretSource link : https://github.com/hvac/hvac/blob/main/hvac/api/secrets_engines/database.pyresp3 = client.secrets.database.generate_credentials( For Database Secret Engine - Static RoleSource link : https://github.com/hvac/hvac/blob/main/hvac/api/secrets_engines/database.pyresp4 = client.secrets.database.get_static_credentials( |
hello :) i've been looking at dynamic secrets and can work on documenting this. I've just started trying out the different dynamic secrets methods that's already in the code. I'm testing it against a local postgres db and can document the code snippets as i go. I know there are many db plugins and each of them have their own nuances, but i'm thinking for the documentation, i could provide the code examples for postgres and reference the vault documentation for details to update on specific plugins - https://developer.hashicorp.com/vault/docs/secrets/databases#database-capabilities Let me know if this sounds like a decent approach and ill get started! would appreciate an additional set of eyes to look over. Ill prob start with a few methods around configuring the connection, roles first. |
Hi @amiewei , welcome! This sounds like a good approach to me, looking forward to it |
Resolved by #1036 |
hi @Dudesons thanks for the PR! I'm looking forward to this feature. Can you please look into providing docs for the new secret engine?
also, all secret engines should accept adonemount_point
variable with a sensible default so the vault path can be adjusted if necessaryThe text was updated successfully, but these errors were encountered: