|
|
|
|
|
by boardwaalk
2453 days ago
|
|
It seems, to me, like a normal command line tool that has the operations you want would integrate better with workflows. Here you can use “-c” but then you’d have to deal with quoting and such. Seems like a big impedance mismatch to pay for “working directory” functionality. ... I don’t have a super tree of Vault secrets though (it’s one level, actually). |
|
The "-c" is mainly intended for automation if needed.
Main motivation behind this project is that I am currently working with rather large secret trees and will have to move them around for upcoming refactors. I could also write scripts for that with the vault client of course .. but it felt to me easier and more flexible on the long-run to have a shell-like approach to work with. In my case, the refactor will include a shift from KV1 to KV2, which is also covered by that tool.
Further, I saw this as an opportunity to do some coding :)