Go to file
James Bardin cfefeec926 walkDestroy is a form of "apply"
When computing the count value, make sure to include walkDestroy with
walkApply, as the former is only a special case of the latter.

When applying a saved plan, the computed count values are lost and we
can no longer query the state for those values. The apply walk was
already considered in the `resourceCountMax` function, but the destroy
walk was not.  This worked when destroying in a single operation
("terraform destroy"), since the state would still be updated with the
latest counts from the plan.
2018-04-10 11:46:29 -04:00
.github issue template: "additional context" instead of "important factoids" 2018-01-03 15:25:54 -08:00
backend backend/manta: Add support for manta backend tiered path structure 2018-04-03 17:32:10 +03:00
builtin Merge pull request #17781 from hashicorp/jbardin/habitat 2018-04-05 08:43:50 -04:00
command Merge pull request #17711 from hashicorp/jbardin/cleanup-temps 2018-03-28 14:06:21 -04:00
communicator connect communicator during Start 2018-04-05 12:54:58 -04:00
config update missing alias message 2018-04-03 17:40:36 -04:00
configs configs: allow full type constraints for variables 2018-03-08 16:23:35 -08:00
contrib Update README.md 2018-03-08 17:41:51 +09:00
dag faster DAG transitive reduction 2017-10-03 11:24:59 -04:00
digraph Fix TestWriteDot random order error 2014-07-29 10:26:50 -07:00
docs mons-months: fix typo in maintainer-etiquette 2017-09-25 17:29:19 +02:00
e2e e2e: allow tests to set environment variables for command runs 2017-09-28 14:35:51 -07:00
examples Microsoft Azure -> Azure 2017-11-07 15:35:34 +00:00
flatmap flatmap: be resilient to lying "foo.#" key 2017-06-23 14:47:36 -07:00
helper helper/schema: ResourceDiff ForceNew attribute correctness 2018-04-08 07:50:41 -07:00
httpclient Allow callers to append to user agent 2018-03-15 10:53:44 -04:00
moduledeps plugin/discovery: PluginRequirements can specify SHA256 digests 2017-06-09 14:03:59 -07:00
plugin Standardize http.Client creation with User-Agent 2018-02-28 12:09:50 -05:00
registry Standardize http.Client creation with User-Agent 2018-02-28 12:09:50 -05:00
repl repl: fix formatting of list and map values 2018-03-28 14:43:45 -07:00
scripts Uses the current working directory to name the built binary 2017-10-30 10:49:47 -07:00
state Merge pull request #17431 from oscr/use-seekstart 2018-04-04 15:27:24 -04:00
svchost Standardize http.Client creation with User-Agent 2018-02-28 12:09:50 -05:00
terraform walkDestroy is a form of "apply" 2018-04-10 11:46:29 -04:00
test-fixtures main: allow overriding host-based discovery in CLI config 2017-10-26 08:58:52 -07:00
tfdiags Update various files for new version of "stringer" 2017-12-11 13:26:29 -08:00
tools/terraform-bundle tools/terraform-bundle: compress files in the generated zip file 2018-04-06 19:16:25 -07:00
vendor udpate winrmcp 2018-04-05 12:54:58 -04:00
version release: clean up after v0.11.6 2018-04-05 19:42:26 +00:00
website Update guides.erb 2018-04-09 15:11:59 -05:00
.gitignore gitignore should ignore test files that use .terraform/tfstate 2017-01-26 14:33:49 -08:00
.travis.yml update travis to go1.10.1 2018-04-05 15:09:09 -04:00
BUILDING.md Makefile/docs: Lock in 1.6 req, doc vendored deps 2016-02-24 16:13:49 -06:00
CHANGELOG.md Add a little more explanation for GH-17811 in CHANGELOG.md 2018-04-09 15:58:12 -07:00
Dockerfile build: Stop using deprecated MAINTAINER in Dockerfile 2017-10-27 17:25:44 -07:00
LICENSE Adding license 2014-07-28 13:54:06 -04:00
Makefile finish removing vet from the makefile 2018-02-21 15:30:29 -05:00
README.md Update README.md (#16653) 2017-11-16 16:15:16 -06:00
Vagrantfile Start building with Terraform 1.9 2017-08-28 09:59:30 -07:00
checkpoint.go fixing version numbers RCs should be labeled x.x.x-rcx 2015-02-07 16:56:56 +01:00
commands.go use the new Meta.ShutdownCh when building commands 2017-12-01 13:14:44 -05:00
config.go main: allow overriding host-based discovery in CLI config 2017-10-26 08:58:52 -07:00
config_test.go main: allow overriding host-based discovery in CLI config 2017-10-26 08:58:52 -07:00
config_unix.go Use build-in method to get user homedir instead of eval on sh 2018-03-21 14:55:56 +01:00
config_windows.go config looks in a plugin directory if it exists 2014-09-27 12:36:13 -07:00
help.go Remind future maintainers to update the docs when changing CLI usage 2016-11-24 09:22:18 -08:00
main.go main: don't print the CLI config into the logs 2017-11-14 15:49:26 -08:00
main_test.go main: make configuration available when initializing commands 2017-09-29 14:03:09 -07:00
panic.go panic: Instruct the user to include terraform's version for bug reports. 2015-05-14 18:14:56 -04:00
plugins.go keep .terraform.d/plugins for discovery 2017-08-09 17:46:49 -04:00
signal_unix.go Forward SIGTERM and handle that as an interrupt 2016-12-08 12:20:25 -05:00
signal_windows.go Forward SIGTERM and handle that as an interrupt 2016-12-08 12:20:25 -05:00
synchronized_writers.go main: synchronize writes to VT100-faker on Windows 2017-05-04 15:36:51 -07:00
version.go use the new version package 2017-10-19 21:48:08 -04: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

If you're new to Terraform and want to get started creating infrastructure, please checkout our Getting Started guide, available on the Terraform website.

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.9+ 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.

This repository contains only Terraform core, which includes the command line interface and the main graph engine. Providers are implemented as plugins that each have their own repository in the terraform-providers organization on GitHub. Instructions for developing each provider are in the associated README file. For more information, see the provider development overview.

For local development of Terraform core, first make sure Go is properly installed and that a GOPATH has been set. 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 which has not been separated into an individual repository and only wish to rebuild that provider, you can use the plugin-dev target. For example, to build only the Test provider:

$ make plugin-dev PLUGIN=provider-test

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, 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.

Docker

When using docker you don't need to have any of the Go development tools installed and you can clone terraform to any location on disk (doesn't have to be in your $GOPATH). This is useful for users who want to build master or a specific branch for testing without setting up a proper Go environment.

For example, run the following command to build terraform in a linux-based container for macOS.

docker run --rm -v $(pwd):/go/src/github.com/hashicorp/terraform -w /go/src/github.com/hashicorp/terraform -e XC_OS=darwin -e XC_ARCH=amd64 golang:latest bash -c "apt-get update && apt-get install -y zip && make bin"

License

FOSSA Status