This is a "should never happen" case, but we have reports of it actually happening. In order to try to collect a bit more data about what's going on here, we're changing what was previously a hard panic into a normal error message that can include the address of the instance we were working on and the action we were trying to do to it at the time. The hope is to narrow down what situations can trigger this in order to find a reliable reproduction case in order to debug further. This also means that for those who _do_ encounter this problem in the meantime Terraform will have a chance to shut down cleanly and therefore be more likely to be able to recover on a subsequent plan/apply cycle. Further investigation of this will follow once we see a report or two of this updated error message. |
||
---|---|---|
.github | ||
addrs | ||
backend | ||
builtin | ||
command | ||
communicator | ||
config | ||
configs | ||
contrib | ||
dag | ||
digraph | ||
docs | ||
e2e | ||
examples | ||
experiments | ||
flatmap | ||
helper | ||
httpclient | ||
internal | ||
lang | ||
moduledeps | ||
plans | ||
plugin | ||
providers | ||
provisioners | ||
registry | ||
repl | ||
scripts | ||
state | ||
states | ||
terraform | ||
tfdiags | ||
tools | ||
vendor | ||
version | ||
website | ||
.gitignore | ||
.go-version | ||
.hashibot.hcl | ||
.tfdev | ||
.travis.yml | ||
BUILDING.md | ||
CHANGELOG.md | ||
checkpoint.go | ||
CODEOWNERS | ||
commands.go | ||
config.go | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
help.go | ||
LICENSE | ||
main_test.go | ||
main.go | ||
Makefile | ||
panic.go | ||
plugins.go | ||
README.md | ||
signal_unix.go | ||
signal_windows.go | ||
synchronized_writers.go | ||
version.go |
Terraform
- Website: https://www.terraform.io
- Mailing list: Google Groups
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
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.
To learn more about compiling Terraform and contributing suggested changes, please refer to the contributing guide.