News for hackers. Stuff that matters.
Re:Hashicorp Vault v1.0 by zimbatm on Tuesday December 04, 2018 @03:28PM (#18603320)
Anther solution is to store secrets in the Terraform state and use a secured state backend (eg: S3+KMS) to share them. It makes key sharing and rotation a bit easier while not promoting copy-and-paste.

You can use the "random" provider to generate secrets, the "tls" provider to generate certs and I also wrote a "secret" provider[1] to hold arbitrary secrets.

The best part is that it doesn't require to maintain a long-running process. For small shops it's a good upgrade over storing credentials in code or using git-crypt.

[1]: https://github.com/tweag/terraform-provider-secret

Re:Hashicorp Vault v1.0 by yeukhon on Tuesday December 04, 2018 @08:58PM (#18605177)
You don't want to store secrets in state files. Imagine you run a CI/CD system where you run terraform plan. Now secrets is all public.
Re:Hashicorp Vault v1.0 by toomuchtodo on Tuesday December 04, 2018 @10:29PM (#18605484)
https://github.com/hashicorp/terraform/issues/516

TLDR: Terraform should use Vault for storing secrets in state, but does not support it yet.

(it is occasionally unavoidable storing secrets in state due to resources orchestrated)

Re:Hashicorp Vault v1.0 by zimbatm on Wednesday December 05, 2018 @04:25AM (#18606816)
That's fine. Secrets are market as "sensitive" and not displayed in the plan output.