github.com/tushar-armorcode/terraform@v0.11.12-beta1/README.md (about) 1 Terraform 2 ========= 3 4 - Website: https://www.terraform.io 5 - [](https://gitter.im/hashicorp-terraform/Lobby) 6 - Mailing list: [Google Groups](http://groups.google.com/group/terraform-tool) 7 8 <img alt="Terraform" src="https://cdn.rawgit.com/hashicorp/terraform-website/master/content/source/assets/images/logo-hashicorp.svg" width="600px"> 9 10 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. 11 12 The key features of Terraform are: 13 14 - **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. 15 16 - **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. 17 18 - **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. 19 20 - **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. 21 22 For more information, see the [introduction section](http://www.terraform.io/intro) of the Terraform website. 23 24 Getting Started & Documentation 25 ------------------------------- 26 27 If you're new to Terraform and want to get started creating infrastructure, please checkout our [Getting Started](https://www.terraform.io/intro/getting-started/install.html) guide, available on the [Terraform website](http://www.terraform.io). 28 29 All documentation is available on the [Terraform website](http://www.terraform.io): 30 31 - [Intro](https://www.terraform.io/intro/index.html) 32 - [Docs](https://www.terraform.io/docs/index.html) 33 34 Developing Terraform 35 -------------------- 36 37 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.11+ 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. 38 39 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). 40 41 For local development of Terraform core, first make sure Go is properly installed and that a 42 [GOPATH](http://golang.org/doc/code.html#GOPATH) has been set. You will also need to add `$GOPATH/bin` to your `$PATH`. 43 44 Next, using [Git](https://git-scm.com/), clone this repository into `$GOPATH/src/github.com/hashicorp/terraform`. 45 46 You'll need to run `make tools` to install some required tools, then `make`. This will compile the code and then run the tests. If this exits with exit status 0, then everything is working! 47 You only need torun `make tools` once (or when the tools change). 48 49 ```sh 50 $ cd "$GOPATH/src/github.com/hashicorp/terraform" 51 $ make tools 52 $ make 53 ``` 54 55 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: 56 57 ```sh 58 $ make dev 59 ... 60 $ bin/terraform 61 ... 62 ``` 63 64 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. 65 66 ```sh 67 $ make test TEST=./terraform 68 ... 69 ``` 70 71 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: 72 73 ```sh 74 $ make plugin-dev PLUGIN=provider-test 75 ``` 76 77 ### Dependencies 78 79 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. 80 81 If you're developing Terraform, there are a few tasks you might need to perform. 82 83 #### Adding a dependency 84 85 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. 86 87 To add a dependency: 88 89 Assuming your work is on a branch called `my-feature-branch`, the steps look like this: 90 91 1. Add the new package to your GOPATH: 92 93 ```bash 94 go get github.com/hashicorp/my-project 95 ``` 96 97 2. Add the new package to your `vendor/` directory: 98 99 ```bash 100 govendor add github.com/hashicorp/my-project/package 101 ``` 102 103 3. Review the changes in git and commit them. 104 105 #### Updating a dependency 106 107 To update a dependency: 108 109 1. Fetch the dependency: 110 111 ```bash 112 govendor fetch github.com/hashicorp/my-project 113 ``` 114 115 2. Review the changes in git and commit them. 116 117 ### Acceptance Tests 118 119 Terraform has a comprehensive [acceptance 120 test](http://en.wikipedia.org/wiki/Acceptance_testing) suite covering the 121 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. 122 123 124 ### Cross Compilation and Building for Distribution 125 126 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. 127 128 For example, to compile 64-bit Linux binaries on Mac OS X, you can run: 129 130 ```sh 131 $ XC_OS=linux XC_ARCH=amd64 make bin 132 ... 133 $ file pkg/linux_amd64/terraform 134 terraform: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped 135 ``` 136 137 `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: 138 139 ```sh 140 $ XC_OS="linux darwin" XC_ARCH="386 amd64" make bin 141 ... 142 $ tree ./pkg/ -P "terraform|*.zip" 143 ./pkg/ 144 ├── darwin_386 145 │ └── terraform 146 ├── darwin_386.zip 147 ├── darwin_amd64 148 │ └── terraform 149 ├── darwin_amd64.zip 150 ├── linux_386 151 │ └── terraform 152 ├── linux_386.zip 153 ├── linux_amd64 154 │ └── terraform 155 └── linux_amd64.zip 156 157 4 directories, 8 files 158 ``` 159 160 _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._ 161 162 #### Docker 163 164 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. 165 166 For example, run the following command to build terraform in a linux-based container for macOS. 167 168 ```sh 169 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" 170 ``` 171 172 173 ## License 174 [](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Fhashicorp%2Fterraform?ref=badge_large)