-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform Integration #318
Comments
I had a early few thoughts on how we could enable this:
Thinking about this more, I think you'd still need the Torus daemon locally to set and work with the secrets. Having the torus daemon running to Terraform apply would be clunky. Especially, in an automated environment such as CI. It is possible that the plugin could just include components of the Daemon requiring the user to specify a TORUS_EMAIL/TORUS_PASSWORD or TORUS_TOKEN_ID/TORUS_TOKEN_SECRET which the plugin would use to perform a login. It'd still be necessary to have the Torus CLI for all other activities. Although, it may be nice to enabling writing from Terraform, however I'm not sure how important of a use case this is today this would provide to developers. Any and all feedback is appreciated! |
Another possibility is using |
A user can now export secrets from torus to the `tfvars` file format. Related #318
A user can now export secrets from torus to the `tfvars` file format. Related #318
A quick and simple way to get setup using Torus with Terraform would make it really easy for anyone using Terraform to store/share their secrets inside Torus.
To use Torus today with Terraform or Terragrunt via
torus run
you have to:TF_VAR_
torus link
torus run
.This isn't a lot of work, but it's non-obvious, and could be stream lined. After looking at the options, there are really two pathways forward:
torus run
by making it easier or unnecessary to think about 1 and 3.The text was updated successfully, but these errors were encountered: