by medina on 12/12/15, 1:36 AM with 21 comments
by notdonspaulding on 12/12/15, 5:44 AM
We use Vagrant at work and I'm considering whether and how we could use more of their tooling. But I always want to know about the business model behind the tools I recommend before I recommend them.
Anyone?
by borplk on 12/12/15, 3:51 AM
For example let's say I store an API token in Vault and want to use that in my Node.js application.
That means I can't do "var api_token = MY_API_TOKEN;" because the secret needs to come from vault and get refreshed, etc...
I'd imagine you will need some agent to manage the secret lease/expiry and for that to reload your entire application to ensure you don't end up with old secrets hanging around in the memory.
This topic is not addressed anywhere in the Vault documentation, I looked everywhere I could.
by adrtessier on 12/12/15, 2:24 AM
[1] https://lyft.github.io/confidant/ [2] https://square.github.io/keywhiz/
by doublerebel on 12/12/15, 2:11 PM
And yesterday I got it to build and run on SmartOS too, for extra security and scalability. Thanks to Hashicorp team for their work, and their commitment to open-source.