-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Vault list support #229
Comments
By the way, gomplate has been THE missing templating tool for us, and I'm probably using it to do way too much :) |
Hi @tallpauley! Thanks for the kind words, and thanks for the feature request! This is an interesting idea... It may be possible right now in theory - you could try setting the path to So, something like:
I'm not sure if that's ideal, but at least it'd be a start. I'll think about the UX some more and get back to you 🙂 |
This is no longer a requirement for us. In my case I was trying to do a little too much with a templating engine :) |
@tallpauley totally understand - I have to be careful to not overuse gomplate as well 😉 That being said, there may still be a place for a feature like this, maybe in conjunction with the "directory datasource" (#215) idea... I'm still formulating a UX I like, but I'm starting to think it may just be as simple as doing a "list" operation when the path ends in a |
I'm unable to list vault approle secret ID accessors, since you have to LIST (not supported) or do a GET w/ a get string (also not supported). Any good way to support this? Maybe it could be something like the following?
If you have a way you would want this implemented @hairyhenderson, I can submit a PR
The text was updated successfully, but these errors were encountered: