We've been holding on to this snapshot of the old docs from the v0.11 branch ever since the v0.12 release as a courtesy to folks who are still using Terraform v0.11, since until now we didn't have any way to serve older versions' docs on the website alongside the current aside from snapshotting it forward in this way. However, our website framework now supports publishing multiple versions at the same time and so the final resting place for these v0.11 docs will be in the "v1.1" branch, whose content is serving as the documentation for the "v1.1 and earlier" version selection on the website. While it does still feel a little awkward to have v0.11 be a subsection of the v1.1 docs, this is at least more honest in that v0.11 _is_ earlier than v1.1, whereas it's confusing and weird for it to appear under the "v1.2.x" option and the other versions that will appear later. In order to avoid breaking incoming links to the old docs we will deploy this in conjunction with some additional redirects managed by the top-level terraform-website repository, which will send all paths with the prefix /language/configuration-0-11 to the equivalent path under /language/v1.1.x/configuration-0-11 . That redirect rule must exist outside of this repository because it's a bridge _between_ versions of the website in this repository, rather than a link to other content within the same version. |
||
---|---|---|
.github | ||
.release | ||
docs | ||
internal | ||
scripts | ||
tools | ||
version | ||
website | ||
.gitignore | ||
.go-version | ||
.tfdev | ||
BUGPROCESS.md | ||
CHANGELOG.md | ||
checkpoint.go | ||
codecov.yml | ||
CODEOWNERS | ||
commands.go | ||
Dockerfile | ||
experiments.go | ||
go.mod | ||
go.sum | ||
help.go | ||
LICENSE | ||
main_test.go | ||
main.go | ||
Makefile | ||
plugins.go | ||
provider_source.go | ||
README.md | ||
signal_unix.go | ||
signal_windows.go | ||
tools.go | ||
version.go | ||
working_dir.go |
Terraform
- Website: https://www.terraform.io
- Forums: HashiCorp Discuss
- Documentation: https://www.terraform.io/docs/
- Tutorials: HashiCorp's Learn Platform
- Certification Exam: HashiCorp Certified: Terraform Associate
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, refer to the What is Terraform? page on the Terraform website.
Getting Started & Documentation
Documentation is available on the Terraform website:
If you're new to Terraform and want to get started creating infrastructure, please check out our Getting Started guides on HashiCorp's learning platform. There are also additional guides to continue your learning.
Show off your Terraform knowledge by passing a certification exam. Visit the certification page for information about exams and find study materials on HashiCorp's learning platform.
Developing Terraform
This repository contains only Terraform core, which includes the command line interface and the main graph engine. Providers are implemented as plugins, and Terraform can automatically download providers that are published on the Terraform Registry. HashiCorp develops some providers, and others are developed by other organizations. For more information, see Extending Terraform.
-
To learn more about compiling Terraform and contributing suggested changes, refer to the contributing guide.
-
To learn more about how we handle bug reports, refer to the bug triage guide.
-
To learn how to contribute to the Terraform documentation in this repository, refer to the Terraform Documentation README.