Why Plan output reading in Terraform? - Purpose & Use Cases

The Big Idea

What if you could see the future of your cloud changes before making them?

The Scenario

Imagine you are building a house by yourself without any blueprint. You try to remember every detail and guess what comes next. This is like managing cloud resources manually without knowing what changes will happen before applying them.

The Problem

Manually guessing changes is slow and risky. You might break something important or waste time fixing unexpected problems. Without a clear preview, you can't be sure what will happen when you make updates.

The Solution

Plan output reading in Terraform acts like a clear blueprint. It shows you exactly what changes will happen before you apply them. This helps you avoid surprises and make confident decisions.

Before vs After

✗ Before

terraform apply
# Wait and hope nothing breaks

✓ After

terraform plan
# Review changes carefully before applying

What It Enables

It lets you see and understand all upcoming changes, so you can prevent mistakes and manage cloud resources safely and efficiently.

Real Life Example

Before updating a website server, you run a plan to check if the update will add new servers or remove existing ones, avoiding accidental downtime.

Key Takeaways

Manual updates can cause unexpected errors.

Plan output reading previews changes clearly.

This helps you manage cloud resources safely and confidently.

Practice

1. What does the terraform plan command primarily show before applying changes?

easy

A. The current cost of your cloud resources

B. The changes Terraform will make to your infrastructure

C. The list of all Terraform providers installed

D. The history of previous Terraform apply commands

Solution

1. Step 1: Understand the purpose of terraform plan

   This command previews the changes Terraform will perform on your infrastructure without applying them.

2. Step 2: Compare options with command purpose

   Only The changes Terraform will make to your infrastructure correctly describes this preview of changes. Other options describe unrelated information.

3. Final Answer:

   The changes Terraform will make to your infrastructure -> Option B

4. Quick Check:

   Plan shows changes = B [OK]

Hint: Plan shows what changes will happen before apply [OK]

Common Mistakes:

• Confusing plan with apply
• Thinking plan shows costs
• Assuming plan shows provider list

2. In Terraform plan output, what does the symbol ~ indicate?

easy

A. Resource will be updated

B. Resource will be created

C. Resource will be deleted

D. Resource will be ignored

Solution

1. Step 1: Recall Terraform plan symbols

   The symbol ~ means a resource will be updated (changed in place).

2. Step 2: Match symbol to meaning

   + means create, - means delete, so ~ must mean update.

3. Final Answer:

   Resource will be updated -> Option A

4. Quick Check:

   ~ means update = A [OK]

Hint: Remember + create, ~ update, - delete symbols [OK]

Common Mistakes:

• Mixing up ~ with + or -
• Thinking ~ means delete
• Assuming ~ means no change

3. Given this Terraform plan output snippet:

  # aws_instance.web will be updated in-place
  ~ resource "aws_instance" "web" {
      instance_type = "t2.micro" -> "t2.small"
    }

What does this output mean?

medium

A. The instance type will change from t2.micro to t2.small

B. No changes will be made to the instance

C. The instance will be deleted and recreated

D. The instance will be created new

Solution

1. Step 1: Analyze the plan output details

   The symbol ~ shows an in-place update. The instance_type changes from "t2.micro" to "t2.small".

2. Step 2: Interpret the meaning

   This means the existing instance will be updated to the new type without deletion.

3. Final Answer:

   The instance type will change from t2.micro to t2.small -> Option A

4. Quick Check:

   ~ means update, instance_type changed = C [OK]

Hint: Look for ~ and arrow showing old -> new value [OK]

Common Mistakes:

• Thinking resource will be deleted
• Ignoring the arrow showing value change
• Assuming no change because resource exists

4. You see this Terraform plan output:

  # aws_s3_bucket.example will be deleted
  - resource "aws_s3_bucket" "example" {
      bucket = "my-bucket"
    }

But you want to keep the bucket. What should you do?

medium

A. Ignore the plan and continue

B. Remove the resource from your Terraform config

C. Run terraform apply immediately

D. Add lifecycle rule with prevent_destroy to the resource

Solution

1. Step 1: Understand the delete plan

   The plan shows the bucket will be deleted, but you want to keep it.

2. Step 2: Use lifecycle prevent_destroy

   Adding a lifecycle block with prevent_destroy = true stops accidental deletion.

3. Final Answer:

   Add lifecycle rule with prevent_destroy to the resource -> Option D

4. Quick Check:

   Use prevent_destroy to block deletes = A [OK]

Hint: Use lifecycle prevent_destroy to stop unwanted deletes [OK]

Common Mistakes:

• Removing resource causes deletion
• Applying plan deletes bucket
• Ignoring plan risks data loss

5. You run terraform plan and see:

  # aws_security_group.sg will be replaced
  - resource "aws_security_group" "sg" {
      name = "old-sg"
    }
  + resource "aws_security_group" "sg" {
      name = "new-sg"
    }

What does this mean and why does Terraform replace the resource instead of updating it?

hard

A. Terraform will fail because name change is not allowed

B. Terraform updates the resource in place changing the name

C. Terraform deletes and recreates because the name attribute is immutable

D. Terraform ignores the change because names can be duplicated

Solution

1. Step 1: Analyze the plan output for replacement

   The plan shows the resource will be deleted (-) and a new one created (+) with a different name.

2. Step 2: Understand why replacement occurs

   Some attributes like security group name are immutable, so Terraform must replace the resource to change them.

3. Final Answer:

   Terraform deletes and recreates because the name attribute is immutable -> Option C

4. Quick Check:

   Immutable attribute change causes replacement = D [OK]

Hint: Immutable attribute changes cause resource replacement [OK]

Common Mistakes:

• Thinking Terraform updates name in place
• Assuming name can be duplicated
• Believing plan will fail on name change