Re:An Interactive HashiCorp Vault Shell
by lingrino on Tuesday October 08, 2019 @09:47AM
(#21192232)
Very cool! I have a very similar (non-interactive) project for copy/move/search on folders. It's something I think should be added to the vault core but there doesn't seem to be much interest there.
Re:An Interactive HashiCorp Vault Shell
by boardwaalk on Tuesday October 08, 2019 @09:42AM
(#21192177)
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).
Re:An Interactive HashiCorp Vault Shell
by fishi0x01 on Tuesday October 08, 2019 @01:29PM
(#21194702)
You are right, it is nothing fancy indeed.
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 :)
A few options exist for Windows already, allowing FUSE filesytem code an easy path to run on Windows. I've recently used winfsp + it's sshfs port, and it works pretty well.
https://github.com/hashicorp/vault/pull/6108
https://github.com/jboero/hashifuse
https://github.com/lingrino/vaku
Thank you for sharing
... 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 :)
https://dokan-dev.github.io/
A few options exist for Windows already, allowing FUSE filesytem code an easy path to run on Windows. I've recently used winfsp + it's sshfs port, and it works pretty well.
Afaik Mac and Unix should be supported by FUSE, so it seems like a viable option.
Are there any reasonable go libraries for FUSE that you can recommend?