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

Customizable secret mount point #25

Closed
stklcode opened this issue Nov 19, 2018 · 1 comment
Closed

Customizable secret mount point #25

stklcode opened this issue Nov 19, 2018 · 1 comment
Milestone

Comments

@stklcode
Copy link
Owner

@stklcode stklcode commented Nov 19, 2018

Prefix for convenience methods like readSecret() is currently hardcoded to secret/. However this path is configurable in Vault.

The more general read() method allows to read from arbitrary paths, however the shorthand variant could be little more flexible.

@stklcode stklcode added this to the 0.8 milestone Nov 19, 2018
stklcode added a commit that referenced this issue Nov 20, 2018
This test does not yet work without changes, because KV v2 is mounted on
 non-standard path and this is not yet supported (see #25).
stklcode added a commit that referenced this issue Mar 17, 2019
The backend can be mounted on an arbitrary path, so this path can now be
passed as an arugment along with the corresponding method call.
stklcode added a commit that referenced this issue Mar 17, 2019
The backend can be mounted on an arbitrary path, so this path can now be
passed as an arugment along with the corresponding method call.
stklcode added a commit that referenced this issue Mar 17, 2019
The backend can be mounted on an arbitrary path, so this path can now be
passed as an arugment along with the corresponding method call.
@stklcode stklcode changed the title Customizable secret prefix Customizable secret mount point Mar 22, 2019
@stklcode
Copy link
Owner Author

@stklcode stklcode commented Mar 23, 2019

For generic secrets the readSecret() equivalent with custom mount point is simply read().

For KV v2 methods readSecretData() accepts a mount parameter and expands the actually read path to <mount>/data/<key>. Same for writing, metadata, etc.

@stklcode stklcode closed this Mar 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant