github.com/sl1pm4t/terraform@v0.6.4-0.20170725213156-870617d22df3/README.md (about)

     1  Terraform
     2  =========
     3  
     4  - Website: https://www.terraform.io
     5  - [![Gitter chat](https://badges.gitter.im/hashicorp-terraform/Lobby.png)](https://gitter.im/hashicorp-terraform/Lobby)
     6  [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fhashicorp%2Fterraform.svg?type=shield)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fhashicorp%2Fterraform?ref=badge_shield)
     7  - Mailing list: [Google Groups](http://groups.google.com/group/terraform-tool)
     8  
     9  ![Terraform](https://www.terraform.io/assets/images/logo-hashicorp.svg)
    10  
    11  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.
    12  
    13  The key features of Terraform are:
    14  
    15  - **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.
    16  
    17  - **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.
    18  
    19  - **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.
    20  
    21  - **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.
    22  
    23  For more information, see the [introduction section](http://www.terraform.io/intro) of the Terraform website.
    24  
    25  Getting Started & Documentation
    26  -------------------------------
    27  
    28  All documentation is available on the [Terraform website](http://www.terraform.io).
    29  
    30  Developing Terraform
    31  --------------------
    32  
    33  If you wish to work on Terraform itself or any of its built-in providers, you'll first need [Go](http://www.golang.org) installed on your machine (version 1.8+ 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.
    34  
    35  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](https://github.com/terraform-providers) on GitHub. Instructions for developing each provider are in the associated README file. For more information, see [the provider development overview](https://www.terraform.io/docs/plugins/provider.html).
    36  
    37  For local development of Terraform core, first make sure Go is properly installed and that a
    38  [GOPATH](http://golang.org/doc/code.html#GOPATH) has been set. You will also need to add `$GOPATH/bin` to your `$PATH`.
    39  
    40  Next, using [Git](https://git-scm.com/), 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!
    41  
    42  ```sh
    43  $ cd "$GOPATH/src/github.com/hashicorp/terraform"
    44  $ make
    45  ```
    46  
    47  To compile a development version of Terraform and the built-in plugins, run `make dev`. This will build everything using [gox](https://github.com/mitchellh/gox) and put Terraform binaries in the `bin` and `$GOPATH/bin` folders:
    48  
    49  ```sh
    50  $ make dev
    51  ...
    52  $ bin/terraform
    53  ...
    54  ```
    55  
    56  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.
    57  
    58  ```sh
    59  $ make test TEST=./terraform
    60  ...
    61  ```
    62  
    63  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:
    64  
    65  ```sh
    66  $ make plugin-dev PLUGIN=provider-test
    67  ```
    68  
    69  ### Dependencies
    70  
    71  Terraform stores its dependencies under `vendor/`, which [Go 1.6+ will automatically recognize and load](https://golang.org/cmd/go/#hdr-Vendor_Directories). We use [`govendor`](https://github.com/kardianos/govendor) to manage the vendored dependencies.
    72  
    73  If you're developing Terraform, there are a few tasks you might need to perform.
    74  
    75  #### Adding a dependency
    76  
    77  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.
    78  
    79  To add a dependency:
    80  
    81  Assuming your work is on a branch called `my-feature-branch`, the steps look like this:
    82  
    83  1. Add the new package to your GOPATH:
    84  
    85      ```bash
    86      go get github.com/hashicorp/my-project
    87      ```
    88  
    89  2.  Add the new package to your `vendor/` directory:
    90  
    91      ```bash
    92      govendor add github.com/hashicorp/my-project/package
    93      ```
    94  
    95  3. Review the changes in git and commit them.
    96  
    97  #### Updating a dependency
    98  
    99  To update a dependency:
   100  
   101  1. Fetch the dependency:
   102  
   103      ```bash
   104      govendor fetch github.com/hashicorp/my-project
   105      ```
   106  
   107  2. Review the changes in git and commit them.
   108  
   109  ### Acceptance Tests
   110  
   111  Terraform has a comprehensive [acceptance
   112  test](http://en.wikipedia.org/wiki/Acceptance_testing) suite covering the
   113  built-in providers. Our [Contributing Guide](https://github.com/hashicorp/terraform/blob/master/.github/CONTRIBUTING.md) includes details about how and when to write and run acceptance tests in order to help contributions get accepted quickly.
   114  
   115  
   116  ### Cross Compilation and Building for Distribution
   117  
   118  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.
   119  
   120  For example, to compile 64-bit Linux binaries on Mac OS X, you can run:
   121  
   122  ```sh
   123  $ XC_OS=linux XC_ARCH=amd64 make bin
   124  ...
   125  $ file pkg/linux_amd64/terraform
   126  terraform: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped
   127  ```
   128  
   129  `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:
   130  
   131  ```sh
   132  $ XC_OS="linux darwin" XC_ARCH="386 amd64" make bin
   133  ...
   134  $ tree ./pkg/ -P "terraform|*.zip"
   135  ./pkg/
   136  ├── darwin_386
   137  │   └── terraform
   138  ├── darwin_386.zip
   139  ├── darwin_amd64
   140  │   └── terraform
   141  ├── darwin_amd64.zip
   142  ├── linux_386
   143  │   └── terraform
   144  ├── linux_386.zip
   145  ├── linux_amd64
   146  │   └── terraform
   147  └── linux_amd64.zip
   148  
   149  4 directories, 8 files
   150  ```
   151  
   152  _Note: Cross-compilation uses [gox](https://github.com/mitchellh/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._
   153  
   154  #### Docker
   155  
   156  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.
   157  
   158  For example, run the following command to build terraform in a linux-based container for macOS.
   159  
   160  ```sh
   161  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"
   162  ```
   163  
   164  
   165  ## License
   166  [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fhashicorp%2Fterraform.svg?type=large)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fhashicorp%2Fterraform?ref=badge_large)