OpenTofu lets you declaratively manage your cloud infrastructure.
Go to file
Mitchell Hashimoto d484d6d6ca Update README
2014-07-28 08:52:42 -07:00
builtin provider/aws: Fixing tests 2014-07-28 11:27:58 -04:00
command command: make state unexported on Meta 2014-07-27 22:58:35 -07:00
config config: nicer error if dir isn't a dir 2014-07-28 08:34:43 -07:00
depgraph depgraph: if a walk func errors, don't walk dependents 2014-07-26 18:03:18 -07:00
digraph digraph: fix docs 2014-07-14 12:10:26 -07:00
flatmap flatmap: never auto-convert ints 2014-07-24 11:41:01 -07:00
helper helper/diff: ComputedAttrsUpdate 2014-07-24 20:25:00 -07:00
plugin plugin: better logging 2014-07-24 07:30:21 -07:00
rpc rpc: fix interface impl 2014-07-22 10:36:37 -07:00
scripts website: add website deploy, tweak fonts 2014-07-28 10:28:41 -04:00
terraform terraform: hooks around provisioners 2014-07-27 09:00:34 -07:00
test-fixtures main: add main config 2014-05-25 17:39:44 -07:00
website website: fix fonts 2014-07-28 11:52:15 -04:00
.gitignore gitignore updates 2014-07-28 11:07:49 -04:00
commands.go Always enable color for now 2014-07-26 14:07:47 -07:00
config_test.go Update config test to handle provisioners 2014-07-10 11:38:57 -07:00
config.go provider/consul: Skeleton 2014-07-25 17:03:17 -04:00
Godeps Adding Godeps 2014-07-22 23:08:41 -04:00
log.go Setup panicwrap 2014-05-30 16:07:26 -07:00
main.go Recognize -version 2014-07-13 10:37:25 -07:00
Makefile Use fork of libucl to control what checkout is used 2014-07-22 19:55:00 -07:00
panic.go Setup panicwrap 2014-05-30 16:07:26 -07:00
README.md Update README 2014-07-28 08:52:42 -07:00
TODO.md providers/aws/aws_eip: support update (reassociation) 2014-07-26 15:53:26 -07:00
Vagrantfile Adding Vagrantfile for cross-compile 2014-07-27 18:16:17 -04:00
version.go Implement CLI, version command 2014-05-24 12:04:43 -07:00

Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions.

The key features of Terraform are:

  • Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.

  • Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.

  • Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.

  • Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors.

For more information, see the introduction section of the Terraform website.

Getting Started & Documentation

All documentation is available on the Terraform website.

Developing Terraform

If you wish to work on Terraform itself or any of its built-in providers, you'll first need Go installed (version 1.2+ is required). Make sure Go is properly installed, including setting up a GOPATH. Make sure Go is compiled with cgo support. You can verify this by running go env and checking that CGOENABLED is set to "1".

Next, install Git, which is needed for some dependencies.

Then, install Gox, which is used as a compilation tool on top of Go:

$ go get -u github.com/mitchellh/gox

Next, clone this repository into $GOPATH/src/github.com/hashicorp/terraform and then just type make. This will compile some dependencies and then run the tests. If this exits with exit status 0, then everything is working!

$ make
...

To compile a development version of Terraform and the built-in plugins, run make dev. This will put Terraform binaries in the bin folder:

$ make dev
...
$ bin/terraform
...

If you're developing a specific package, you can run tests for just that package by specifying the TEST variable. For example below, only terraform package tests will be run.

$ make test TEST=./terraform
...

Acceptance Tests

Terraform also has a comprehensive acceptance test suite covering most of the major features of the built-in providers.

If you're working on a feature of a provider and want to verify it is functioning (and hasn't broken anything else), we recommend running the acceptance tests. Note that we do not require that you run or write acceptance tests to have a PR accepted. The acceptance tests are just here for your convenience.

Warning: The acceptance tests create/destroy/modify real resources, which may incur real costs. In the presence of a bug, it is technically possible that broken providers could corrupt existing infrastructure as well. Therefore, please run the acceptance providers at your own risk. At the very least, we recommend running them in their own private account for whatever provider you're testing.

To run the acceptance tests, invoke make testacc:

$ make testacc TEST=./builtin/providers/aws TESTARGS='-run=VPC'
...

The TEST variable is required, and you should specify the folder where the provider is. The TESTARGS variable is recommended to filter down to a specific resource to test, since testing all of them at once can take a very long time.

Acceptance tests typically require other environment variables to be set for things such as access keys. The provider itself should error early and tell you what to set, so it is not documented here.