Re:Launch HN: EnvKey (YC W18) – Smart Configuration and Secr...
by stevekemp on Monday March 12, 2018 @11:59PM
(#16573808)
I think it's a little weird and biased to imply that Hashicorp's vault needs special setup to manage development secrets.
Vault stores secrets. That's all it does. (Well it can also generate TLS certificates, handle AWS integration and more..) Once you have a vault instance adding a new secret takes seconds and the having an instance for development, and a second for production is trivial.
You can also prefer a single instance with more restrictions, logging, and similar.
Vault stores secrets. That's all it does. (Well it can also generate TLS certificates, handle AWS integration and more..) Once you have a vault instance adding a new secret takes seconds and the having an instance for development, and a second for production is trivial.
You can also prefer a single instance with more restrictions, logging, and similar.
* secret/$application/development/db_user * secret/$application/development/db_pass * secret/$application/development/db_host
vs
* secret/$application/production/db_user * secret/$application/production/db_pass * secret/$application/production/db_host
But the vault itself doesn't care about dev vs. prod. That's more an infrastracture question about which hosts can talk to it, etc.