-
Notifications
You must be signed in to change notification settings - Fork 151
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
Refine vault: config location #488
Comments
It seems context paths are supported now. But I do have one problem with this.
Both of the sets are username/password.
Would it be possible to do something like this?
|
For now, we don't have a possibility to associate a In the context of Vault, only the context path makes sense for inclusion. Additional URL-like elements such as fragment or the query string cannot be applied for mounting so these could be candidates to pass on additional details. For versioned backends, one could also specify |
I think adding support for |
For start, let's go for |
We should accept
vault:
andvault://
config locations as default config location that use enabled secret backend discovery. Additionally, we should acceptvault:///<context-path
(e.g.vault:///secret/my/app/key
) to allow mounting individual context paths without pulling the entire set of all property-enabled secret backends.It does not make sense to accept a hostname since Vault is session-oriented and a custom hostname would conflict with session management.
The text was updated successfully, but these errors were encountered: