dependency graph
Terraform's internal map of every resource, data source and value in a configuration, linked by which depends on which.
In more detail
Terraform builds it from references and depends_on, then walks it to create things in the right order, doing independent ones in parallel. Destroy walks the same graph backwards, so a network is removed after the machines inside it. count and for_each expand the graph into one node per instance during planning.
Related terms
- implicit dependency — An ordering between two resources that Terraform works out for itself because one refers to the other.
- resource reference — An expression such as aws_vpc.main.id that reads a value from another block by its address.
- terraform plan — The command that compares configuration, state and reality and prints the actions needed to make them match, without changing anything.
Taught in
- Providers And The required_providers Block — Infrastructure as Code with Terraform
- Writing Your First Configuration In HCL — Infrastructure as Code with Terraform
- Tearing It Down With Destroy — Infrastructure as Code with Terraform
- Functions And Expressions In HCL — Infrastructure as Code with Terraform
- Querying Existing Infrastructure With Data Sources — Infrastructure as Code with Terraform
- Scaling Resources With Count — Infrastructure as Code with Terraform
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Providers: How Terraform Reaches Every API — HashiCorp Terraform Associate (004) Exam Prep
- Reading A Plan, Saving It, Applying It — HashiCorp Terraform Associate (004) Exam Prep
- Validate, Format, Destroy, And The Flags That Bend A Plan — HashiCorp Terraform Associate (004) Exam Prep
- Dependencies, depends_on And Lifecycle Rules — HashiCorp Terraform Associate (004) Exam Prep
- Verbose Logging: TF_LOG And Friends — HashiCorp Terraform Associate (004) Exam Prep