Terraform apply for execution - Step-by-Step Execution

Process Flow - Terraform apply for execution

Write Terraform config

↓

terraform init

↓

terraform plan

↓

terraform apply

↓

Resources created/updated

↓

terraform state updated

↓

Infrastructure ready

This flow shows how Terraform applies configuration to create or update cloud resources, updating the state to reflect changes.

Execution Sample

Terraform

resource "aws_s3_bucket" "example" {
  bucket = "my-unique-bucket-12345"
  acl    = "private"
}

terraform apply

This code creates a private AWS S3 bucket named 'my-unique-bucket-12345' when 'terraform apply' is run.

Process Table

Step	Action	Evaluation	Result
1	Read Terraform config	Parse resource block	Resource aws_s3_bucket.example identified
2	terraform init	Initialize backend and providers	Providers downloaded, backend configured
3	terraform plan	Compare desired state with current state	Plan shows 1 resource to add
4	terraform apply - confirm	User confirms apply	Apply starts
5	Create aws_s3_bucket.example	Send API request to AWS	Bucket created successfully
6	Update terraform state	Record new resource in state file	State updated with aws_s3_bucket.example
7	Apply complete	No errors	Infrastructure matches config

💡 All resources created successfully, terraform state updated, apply finished

Status Tracker

Variable	Start	After Step 3	After Step 6	Final
terraform_state	empty	shows planned resource	includes aws_s3_bucket.example	final with created resource
resource_status	not created	planned to create	created	created

Key Moments - 3 Insights

Why does terraform plan show changes before apply?

terraform plan compares current state with config and shows what will change; see execution_table step 3.

What happens if user does not confirm apply?

Apply stops before making changes; no resources created; see execution_table step 4.

How does terraform know what resources exist after apply?

It updates the state file after successful creation; see execution_table step 6.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the AWS bucket actually created?

A Step 3

B Step 5

C Step 6

D Step 7

💡 Hint

Check the 'Action' and 'Result' columns in execution_table row 5.

According to variable_tracker, what is the state of 'resource_status' after step 3?

A planned to create

B not created

C created

D deleted

💡 Hint

Look at 'resource_status' value under 'After Step 3' in variable_tracker.

If the user declines confirmation at step 4, what happens to the terraform state?

A State is updated with new resource

B State is deleted

C State remains unchanged

D State is partially updated

💡 Hint

Refer to key_moments about user confirmation and execution_table step 4.

Concept Snapshot

Terraform apply runs after init and plan.
It creates or updates resources to match config.
User confirmation is required before changes.
State file updates after successful apply.
Apply stops if user declines confirmation.

Full Transcript

Terraform apply is the command that makes your cloud resources match your configuration. First, you write your config file describing resources like an AWS S3 bucket. Then you run 'terraform init' to prepare providers. Next, 'terraform plan' shows what changes will happen. When you run 'terraform apply', Terraform asks for confirmation. After you confirm, it creates or updates resources by calling cloud APIs. Once done, it updates the state file to remember what exists. If you do not confirm, no changes happen. This process ensures your cloud matches your desired setup safely and clearly.