Why the workflow matters in Terraform - See It in Action

Why the workflow matters

📖 Scenario: You are setting up a simple cloud infrastructure using Terraform. To keep things organized and avoid mistakes, you need to follow a clear workflow: defining resources, configuring variables, applying the configuration, and finally verifying the setup.

🎯 Goal: Build a Terraform configuration step-by-step that creates a basic AWS S3 bucket, showing why following the Terraform workflow matters for successful infrastructure deployment.

📋 What You'll Learn

Create a Terraform configuration file with an AWS provider

Define an S3 bucket resource with a specific name

Add a variable to configure the bucket name

Apply the configuration following Terraform workflow steps

💡 Why This Matters

🌍 Real World

Terraform is widely used to automate cloud infrastructure setup. Following the workflow ensures your infrastructure is consistent and easy to update.

💼 Career

Cloud engineers and DevOps professionals use Terraform workflows daily to manage infrastructure safely and efficiently.

1

DATA SETUP: Define the AWS provider

Write a Terraform configuration that sets the AWS provider with the region us-east-1. Create a file called main.tf and add the provider block exactly as shown.

Terraform

# Your code here to define the AWS provider with region us-east-1

Hint

The provider block tells Terraform which cloud to work with and where.

2

CONFIGURATION: Add a variable for the bucket name

Add a Terraform variable called bucket_name with a default value of my-terraform-bucket. This variable will let you change the bucket name easily.

Terraform

provider "aws" {
  region = "us-east-1"
}

# Your code here to add variable bucket_name with default my-terraform-bucket

Hint

Variables help keep your configuration flexible and reusable.

3

CORE LOGIC: Define the S3 bucket resource using the variable

Create an AWS S3 bucket resource named my_bucket that uses the variable bucket_name for its bucket name. Use the exact resource block syntax.

Terraform

provider "aws" {
  region = "us-east-1"
}

variable "bucket_name" {
  type    = string
  default = "my-terraform-bucket"
}

# Your code here to define aws_s3_bucket resource my_bucket using var.bucket_name

Hint

Resources define what cloud services you want to create or manage.

4

COMPLETION: Add the Terraform output for the bucket name

Add an output named bucket_id that shows the bucket name after applying the configuration. Use the exact output block syntax referencing aws_s3_bucket.my_bucket.bucket.

Terraform

provider "aws" {
  region = "us-east-1"
}

variable "bucket_name" {
  type    = string
  default = "my-terraform-bucket"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = var.bucket_name
}

# Your code here to add output bucket_id showing aws_s3_bucket.my_bucket.bucket

Hint

Outputs let you see important information after Terraform finishes.

Practice

1. Why is it important to run terraform plan before terraform apply?

easy

A. It shows the changes Terraform will make before applying them

B. It automatically applies changes without confirmation

C. It deletes all existing resources immediately

D. It skips validation of the configuration files

Solution

1. Step 1: Understand the purpose of terraform plan

   This command previews the changes Terraform will make to your infrastructure without applying them.

2. Step 2: Compare with terraform apply

   terraform apply actually makes the changes, so planning first helps avoid mistakes.

3. Final Answer:

   It shows the changes Terraform will make before applying them -> Option A

4. Quick Check:

   Plan previews changes = D [OK]

Hint: Plan first to preview changes, avoid surprises [OK]

Common Mistakes:

• Skipping plan and applying directly
• Thinking plan applies changes
• Confusing plan with destroy

2. Which command correctly initializes a Terraform working directory before planning or applying?

easy

A. terraform init

B. terraform start

C. terraform deploy

D. terraform configure

Solution

1. Step 1: Identify the initialization command

   terraform init sets up the working directory by downloading providers and preparing backend.

2. Step 2: Check other options

   Commands like terraform start, deploy, or configure do not exist in Terraform.

3. Final Answer:

   terraform init -> Option A

4. Quick Check:

   Initialize with init = B [OK]

Hint: Init first to prepare your workspace [OK]

Common Mistakes:

• Using non-existent commands
• Trying to apply before init
• Confusing init with plan

3. Given this Terraform workflow:

terraform init
tf plan
tf apply

What will happen if you run terraform apply without running terraform plan first?

medium

A. Terraform will apply changes immediately without preview

B. Terraform will show an error and stop

C. Terraform will automatically run plan before apply

D. Terraform will delete all resources

Solution

1. Step 1: Understand terraform apply behavior

   Terraform always performs an internal plan, shows the execution plan (preview of changes), and prompts for confirmation before applying.

2. Step 2: Check if plan is mandatory

   Running terraform plan first is recommended for detailed review and saving plans, but terraform apply automatically runs the plan step.

3. Final Answer:

   Terraform will automatically run plan before apply -> Option C

4. Quick Check:

   Apply auto-runs plan [OK]

Hint: Apply always plans first internally [OK]

Common Mistakes:

• Assuming apply always errors without plan
• Thinking apply auto-runs plan silently
• Believing apply deletes resources by default

4. You ran terraform apply but noticed unexpected resource deletions. What is the most likely cause related to workflow?

medium

A. Running terraform init twice

B. Skipping terraform plan and not reviewing changes

C. Using an outdated Terraform version

D. Not setting environment variables

Solution

1. Step 1: Identify workflow mistake

   Skipping terraform plan means you miss previewing changes, leading to surprises like deletions.

2. Step 2: Evaluate other options

   Running init twice, outdated version, or missing env vars usually cause errors, not unexpected deletions.

3. Final Answer:

   Skipping terraform plan and not reviewing changes -> Option B

4. Quick Check:

   Skip plan = risk of unwanted deletions [OK]

Hint: Always plan and review before applying [OK]

Common Mistakes:

• Ignoring plan output
• Blaming init for deletions
• Assuming version causes deletions

5. You want to safely update your cloud infrastructure with Terraform. Which workflow sequence best prevents downtime and mistakes?

hard

A. terraform plan -> terraform apply -> terraform init

B. terraform apply -> terraform plan -> terraform init

C. terraform apply -> terraform init -> terraform plan

D. terraform init -> terraform plan -> review plan -> terraform apply

Solution

1. Step 1: Understand the correct workflow order

   First, terraform init prepares the workspace, then terraform plan previews changes, followed by reviewing the plan carefully.

2. Step 2: Apply changes only after review

   Applying changes after review ensures safety and avoids downtime or mistakes.

3. Final Answer:

   terraform init -> terraform plan -> review plan -> terraform apply -> Option D

4. Quick Check:

   Init, plan, review, apply = C [OK]

Hint: Init, plan, review, then apply for safe updates [OK]

Common Mistakes:

• Applying before planning
• Skipping plan review
• Running commands in wrong order