Why the workflow matters in Terraform - Visual Breakdown

Process Flow - Why the workflow matters

Write Terraform Code

↓

terraform init

↓

terraform plan

↓

terraform apply

↓

Infrastructure Created

↓

terraform destroy (optional)

This flow shows the key steps in Terraform workflow: writing code, initializing, planning, applying, and optionally destroying infrastructure.

Execution Sample

Terraform

terraform init
terraform plan
terraform apply

This sequence initializes Terraform, shows the planned changes, and applies them to create infrastructure.

Process Table

Step	Command	Action	Result	Next Step
1	terraform init	Setup backend and providers	Terraform ready to run plans	terraform plan
2	terraform plan	Check what changes will happen	Shows planned infrastructure changes	terraform apply
3	terraform apply	Create or update infrastructure	Infrastructure created or updated	End or terraform destroy
4	terraform destroy	Remove infrastructure	Infrastructure removed	End

💡 Workflow ends after infrastructure is created or destroyed.

Status Tracker

Variable	Start	After init	After plan	After apply	After destroy
Terraform State	empty	initialized	planned	applied	destroyed
Infrastructure	none	none	none	exists	none

Key Moments - 3 Insights

Why do we run 'terraform plan' before 'terraform apply'?

Running 'terraform plan' shows what changes Terraform will make without applying them. This helps avoid surprises and errors, as seen in step 2 of the execution_table.

What happens if we skip 'terraform init'?

'terraform init' sets up necessary plugins and backend. Skipping it means Terraform cannot run plans or apply changes properly, as shown in step 1.

Why might we use 'terraform destroy'?

'terraform destroy' removes all created infrastructure safely. It is useful for cleaning up resources and avoiding costs, as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after running 'terraform plan'?

A Shows planned infrastructure changes

B Infrastructure created or updated

C Terraform ready to run plans

D Infrastructure removed

💡 Hint

Check the 'Result' column for step 2 in the execution_table.

At which step does the infrastructure actually get created?

A terraform init

B terraform plan

C terraform apply

D terraform destroy

💡 Hint

Look at the 'Action' and 'Result' columns in the execution_table for step 3.

If you skip 'terraform init', what will happen to the Terraform state variable after the first command?

A It becomes 'initialized'

B It stays 'empty'

C It becomes 'planned'

D It becomes 'applied'

💡 Hint

Refer to the variable_tracker row for 'Terraform State' after 'init'.

Concept Snapshot

Terraform workflow steps:
1. terraform init - prepares Terraform
2. terraform plan - previews changes
3. terraform apply - makes changes
4. terraform destroy - removes resources
Following this order avoids errors and surprises.

Full Transcript

The Terraform workflow is important because it guides you through safe and predictable infrastructure changes. First, you write your Terraform code. Then you run 'terraform init' to set up necessary tools. Next, 'terraform plan' shows what changes will happen without applying them. After reviewing, 'terraform apply' creates or updates your infrastructure. Optionally, 'terraform destroy' removes all created resources. Skipping steps can cause errors or unexpected results. This workflow helps you manage cloud resources confidently and avoid mistakes.