npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@cda0/terrajs

v0.6.1

Published

A node interface to Terraform

Downloads

48

Readme

Terrajs

Build Status npm version

A module to help with creating Terraform commands.

Supported Commands

  • apply
  • fmt
  • get
  • graph
  • import
  • init
  • output
  • plan
  • providers
  • refresh
  • show
  • taint
  • untaint
  • validate
  • version
  • workspace
    • delete
    • list
    • new
    • select
    • show

Usage

Terrajs will run Terraform commands from the directory passed in with terraformDir.

const tf = new Terrajs( { terraformDir: 'path/to/configuration' } );
await tf.init({ backendConfig: { key: 'MY_KEY' } });

To view the generated Terraform command without running:

const tf = new Terrajs({ execute: false, terraformDir: 'path/to/configuration' });
console.log(await tf.init({ backendConfig: { key: 'MY_KEY' } }));

If you need to use a Terraform binary that's not on your path as terraform, then you can tell Terrajs where to find it in the constructor.

const tf = new Terrajs( { command: 'terraform12', terraformDir: 'path/to/configuration' } );
await tf.init({ backendConfig: { key: 'MY_KEY' } });

See example.js for a quick impression of how to use the extra commands.

Variables

Variables are mapped from JavaScript camelCase convention to Terraform CLI snake_case convention. For example:

await tf.plan({
  var: {
    subscriptionId: '123',
    tenantId: 'abc',
    zones: ['A', 'B'],
  }
});

...will be mapped to the following command:

terraform plan -var "subscription_id=123" -var "tenant_id=abc" -var 'zones=["A","B"]'

...or on Windows (Command Prompt):

terraform plan -var "subscription_id=123" -var "tenant_id=abc" -var "zones=[\"A\",\"B\"]"

If variables are not being represented as you expect, please set TF_LOG=trace and check to see what Terraform is receiving. Terrajs uses the default shell assumed by child_process which is generally /bin/sh and cmd.exe (on Windows). If a variable's value is quite complex with special characters, this may cause problems with the shell's interpolation.

Test

npm run test

Coverage

npm run coverage

Contributing

Terraform commands live in the templates directory.

Each command has a line for each partial, found in the partials directory.

A partial contains the logic for a command line argument.