cgpuglie
commented
6 years ago Hi Paul,
I originally intended this project to be used with a web application that would allow users to generate terraform configs through a UI. It should be given a single config and an optional state, both as JavaScript objects, which it would use to create a temporary file structure to run terraform from. The configs should follow Terraform's JSON syntax, which can be found here: https://www.terraform.io/docs/configuration/syntax.html#json-syntax .
Each subsequent call returns the resulting state from running Terraform as a JavaScript object, which could then be stored in an object store or something similar for later use.
The library does not have any built in Vault support, but there are definitely a few options for incorporating Vault into it's use.
- You could use Terraform's Vault provider to retrieve secrets for use in your configs: https://www.terraform.io/docs/providers/vault/index.html
- You could use NodeJS to communicate with Vault and inject the secrets into your terraform configs before passing them to node-terraform
I'm sure there are other means of accomplishing this as well.
Since the Web UI lost traction, I haven't been working on this project actively, and as such don't have any real world examples readily available. If you're still interested in using it, I'd be happy to add some documentation as well as do further testing to ensure it behaves as expected.
Great to hear someone may have a use for this project!
Thanks,
Cody
On Mon, Oct 30, 2017 at 10:58 AM, Paul Verdone notifications@github.com wrote:
First, this is not an issue, but more of a thank you for creating this, and a few question on how you intended to use this code.
- Is this referencing an existing folder that has a working terraform set of files (vars and Main), or is this intended to pull secrets and details out of a vault and build folders dynamically and execute them? Or Both? :)
(I have a deployment api that talks to Marathon and several other orchestration tools to launch and manage containers. This is where I keep all the access secrets in Vault and through Vault to Consul, all with direct access from Node.js/Hapi api. Is this what you were using this NPM for? Or just running/executing Terraform folders already populated?)
(Right now I have Terraform creating and provisioning new AWS Mesos Agent Instances standalone and I wanted to add them to my secure api control instance scaling)
(Trying to figure out the variables I am passing in to your NPM).
Any advice, examples or theory of usage appreciated. Again, nice of you to create this.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cgpuglie/node-terraform/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AKO3N1B2BqJc20cIoX6sgZbkGBQU1dKuks5sxg5BgaJpZM4QLmq4 .
💥 anticipation accumulates! ✨