Go to file
James Bardin 82b1a2abc2 Add graph transformation recording
The external api provided here is simply
dag.Graph.SetDebugWriter(io.Writer). When a writer is provided to a
Graph, it will immediately encode itself to the stream, and subsequently
encode any additional transformations to the graph. This will allow
easier logging of graph transformations without writing complete graphs
to the logs at every step. Since the marshalGraph can also be dot
encoded, this will allow translation from the JSON logs to dot graphs.
2016-11-14 08:50:34 -05:00
.github Correct AWS secret key variable name 2016-08-05 14:01:28 +01:00
builtin Merge pull request #10032 from hashicorp/jbardin/vet 2016-11-14 08:49:16 -05:00
command Provider a marshaler for dag.Graph 2016-11-14 08:50:33 -05:00
communicator Remove deprecated key_file and bastion_key_file 2016-10-12 14:30:09 -04:00
config config: update error string for new HIL merge 2016-11-13 10:28:31 -08:00
contrib command: Change module-depth default to -1 2016-01-20 13:58:02 -06:00
dag Add graph transformation recording 2016-11-14 08:50:34 -05:00
deps snapshot from CenturyLinkLabs/terraform-provider-clc 2016-03-21 08:58:37 -07:00
digraph Fix TestWriteDot random order error 2014-07-29 10:26:50 -07:00
examples Merge pull request #6819 from hashicorp/f-aws-vpc-data-sources 2016-10-13 14:17:55 -05:00
flatmap flatmap: never auto-convert ints 2014-07-24 11:41:01 -07:00
helper terraform: default new graphs on, old graphs behind -Xlegacy-graph 2016-11-10 21:53:20 -08:00
plugin plugin: implement ResourceProvider.Stop 2016-10-25 12:08:36 -07:00
scripts Fixed regexp to process comma-separated links to github issues in CHANGELOG.md 2016-10-27 20:07:37 +02:00
state state/remote/swift: Enhancements to support full set of Openstack configuration options, plus SSL certs. Documentation updated to support 2016-11-03 07:36:18 +00:00
terraform Remove dot package 2016-11-14 08:50:34 -05:00
test-fixtures Remove all traces of libucl 2014-08-19 09:57:04 -07:00
vendor vendor: update HIL 2016-11-13 10:28:26 -08:00
website docs/remote_azure: Adding a note to the remote state docs about ENV VARs 2016-11-14 13:26:19 +00:00
.gitignore Do not build supporting JS files 2016-03-22 23:33:40 +02:00
.travis.yml terraform: default new graphs on, old graphs behind -Xlegacy-graph 2016-11-10 21:53:20 -08:00
BUILDING.md Makefile/docs: Lock in 1.6 req, doc vendored deps 2016-02-24 16:13:49 -06:00
CHANGELOG.md Update CHANGELOG.md 2016-11-14 12:12:34 +00:00
LICENSE Adding license 2014-07-28 13:54:06 -04:00
Makefile provider/aws: Run errcheck in tests (#8579) 2016-09-02 09:24:17 -05:00
README.md Update README.md 2016-10-26 00:11:39 +01:00
Vagrantfile Vagrantfile improvement (apt-get) (#8762) 2016-10-26 15:33:40 +01:00
checkpoint.go fixing version numbers RCs should be labeled x.x.x-rcx 2015-02-07 16:56:56 +01:00
commands.go core: Add `terraform state rm` command and docs 2016-08-16 16:45:44 +01:00
config.go core: Log local overrides as INFO rather than WARN 2016-09-14 09:19:03 +01:00
config_test.go Update config test to handle provisioners 2014-07-10 11:38:57 -07:00
config_unix.go core: use !windows instead of a list of unixes 2015-12-30 17:37:24 -05:00
config_windows.go config looks in a plugin directory if it exists 2014-09-27 12:36:13 -07:00
help.go Cleanup main help message to look cleaner 2016-10-10 14:47:35 -04:00
main.go DebugInfo and DebugGraph 2016-11-04 11:30:51 -04:00
panic.go panic: Instruct the user to include terraform's version for bug reports. 2015-05-14 18:14:56 -04:00
version.go Expose Terraform version internally & externally 2015-06-21 12:24:42 +01:00

README.md

Terraform

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 on your machine (version 1.7+ is required). Alternatively, you can use the Vagrantfile in the root of this repo to stand up a virtual machine with the appropriate dev tooling already set up for you.

For local dev first make sure Go is properly installed, including setting up a GOPATH. You will also need to add $GOPATH/bin to your $PATH.

Next, using Git, clone this repository into $GOPATH/src/github.com/hashicorp/terraform. All the necessary dependencies are either vendored or automatically installed, so you just need to type make. This will compile the code and then run the tests. If this exits with exit status 0, then everything is working!

$ cd $GOPATH/src/github.com/hashicorp/terraform
$ make

To compile a development version of Terraform and the built-in plugins, run make dev. This will build everything using gox and put Terraform binaries in the bin and $GOPATH/bin folders:

$ 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, onlyterraform package tests will be run.

$ make test TEST=./terraform
...

If you're working on a specific provider and only wish to rebuild that provider, you can use the plugin-dev target. For example, to build only the Azure provider:

$ make plugin-dev PLUGIN=provider-azure

If you're working on the core of Terraform, and only wish to rebuild that without rebuilding providers, you can use the core-dev target. It is important to note that some types of changes may require both core and providers to be rebuilt - for example work on the RPC interface. To build just the core of Terraform:

$ make core-dev

Dependencies

Terraform stores its dependencies under vendor/, which Go 1.6+ will automatically recognize and load. We use govendor to manage the vendored dependencies.

If you're developing Terraform, there are a few tasks you might need to perform.

Adding a dependency

If you're adding a dependency, you'll need to vendor it in the same Pull Request as the code that depends on it. You should do this in a separate commit from your code, as makes PR review easier and Git history simpler to read in the future.

To add a dependency:

Assuming your work is on a branch called my-feature-branch, the steps look like this:

  1. Add the new package to your GOPATH:

    go get github.com/hashicorp/my-project
    
  2. Add the new package to your vendor/ directory:

    govendor add github.com/hashicorp/my-project/package
    
  3. Review the changes in git and commit them.

Updating a dependency

To update a dependency:

  1. Fetch the dependency:

    govendor fetch github.com/hashicorp/my-project
    
  2. Review the changes in git and commit them.

Acceptance Tests

Terraform has a comprehensive acceptance test suite covering the built-in providers. Our Contributing Guide includes details about how and when to write and run acceptance tests in order to help contributions get accepted quickly.

Cross Compilation and Building for Distribution

If you wish to cross-compile Terraform for another architecture, you can set the XC_OS and XC_ARCH environment variables to values representing the target operating system and architecture before calling make. The output is placed in the pkg subdirectory tree both expanded in a directory representing the OS/architecture combination and as a ZIP archive.

For example, to compile 64-bit Linux binaries on Mac OS X Linux, you can run:

$ XC_OS=linux XC_ARCH=amd64 make bin
...
$ file pkg/linux_amd64/terraform
terraform: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped

XC_OS and XC_ARCH can be space separated lists representing different combinations of operating system and architecture. For example, to compile for both Linux and Mac OS X, targeting both 32- and 64-bit architectures, you can run:

$ XC_OS="linux darwin" XC_ARCH="386 amd64" make bin
...
$ tree ./pkg/ -P "terraform|*.zip"
./pkg/
├── darwin_386
│   └── terraform
├── darwin_386.zip
├── darwin_amd64
│   └── terraform
├── darwin_amd64.zip
├── linux_386
│   └── terraform
├── linux_386.zip
├── linux_amd64
│   └── terraform
└── linux_amd64.zip

4 directories, 8 files

Note: Cross-compilation uses gox, which requires toolchains to be built with versions of Go prior to 1.5. In order to successfully cross-compile with older versions of Go, you will need to run gox -build-toolchain before running the commands detailed above.