Prevent_destroy lifecycle rule in Terraform - Step-by-Step Execution

Process Flow - Prevent_destroy lifecycle rule

Define resource with prevent_destroy

↓

Terraform plan detects destroy

↓

Check lifecycle.prevent_destroy

↓

Block destroy

↓

Error message

Terraform checks if a resource marked with prevent_destroy is about to be destroyed. If yes, it blocks the action and shows an error.

Execution Sample

Terraform

resource "aws_s3_bucket" "example" {
  bucket = "my-bucket"
  lifecycle {
    prevent_destroy = true
  }
}

Defines an S3 bucket resource that Terraform will not allow to be destroyed.

Process Table

Step	Action	Resource State	Lifecycle Rule Check	Result
1	Terraform plan detects resource destroy	Resource exists	Check prevent_destroy	Proceed to check rule
2	Check lifecycle.prevent_destroy	Resource exists	prevent_destroy = true	Destroy blocked
3	Terraform blocks destroy	Resource exists	prevent_destroy enforced	Error: Destroy prevented
4	User cancels destroy	Resource remains	No destroy	No change
5	If prevent_destroy was false	Resource exists	prevent_destroy = false	Destroy allowed

💡 Destroy blocked because prevent_destroy is true on the resource

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
resource_exists	true	true	true	true	true
prevent_destroy	true	true	true	true	true
destroy_allowed	false	false	false	false	false

Key Moments - 2 Insights

Why does Terraform show an error instead of destroying the resource?

Because the lifecycle.prevent_destroy rule is set to true, Terraform blocks any destroy action as shown in execution_table step 3.

What happens if prevent_destroy is set to false or omitted?

Terraform allows the resource to be destroyed normally, as shown in execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution table, at which step does Terraform block the destroy action?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Check the 'Result' column for the step where 'Destroy blocked' and 'Error' appear.

According to the variable tracker, what is the value of 'destroy_allowed' after step 3?

A false

B true

C undefined

D null

💡 Hint

Look at the 'destroy_allowed' row under 'After Step 3' in variable_tracker.

If prevent_destroy was false, what would Terraform do according to the execution table?

A Block destroy and show error

B Allow destroy

C Ignore the resource

D Retry destroy multiple times

💡 Hint

See step 5 in execution_table under 'Result' column.

Concept Snapshot

Terraform lifecycle prevent_destroy rule:
- Add lifecycle { prevent_destroy = true } inside resource block
- Blocks any destroy action on that resource
- Terraform plan errors if destroy attempted
- Useful to protect critical resources from accidental deletion

Full Transcript

This visual execution trace shows how Terraform handles the prevent_destroy lifecycle rule. When a resource is marked with prevent_destroy true, Terraform detects any destroy action during plan and blocks it, showing an error. The resource remains intact. If prevent_destroy is false or omitted, Terraform allows the destroy normally. Variables track resource existence and destroy permission. Key moments clarify why errors occur and what changes if the rule is off. The quiz tests understanding of when and how Terraform blocks destruction.

Practice

1. What does the prevent_destroy lifecycle rule do in Terraform?

easy

A. Stops accidental deletion of a resource

B. Automatically recreates a resource if deleted

C. Prevents updates to a resource

D. Locks the resource to prevent any changes

Solution

1. Step 1: Understand the purpose of prevent_destroy

   The prevent_destroy rule is designed to stop Terraform from deleting a resource accidentally.

2. Step 2: Compare with other lifecycle rules

   Unlike update prevention or locking, it specifically blocks deletion unless the rule is removed.

3. Final Answer:

   Stops accidental deletion of a resource -> Option A

4. Quick Check:

   prevent_destroy stops deletion = A [OK]

Hint: Remember: prevent_destroy means no accidental deletes [OK]

Common Mistakes:

• Thinking it prevents updates instead of deletion
• Confusing it with resource locking
• Assuming it recreates deleted resources automatically

2. Which is the correct way to set the prevent_destroy rule in a Terraform resource?

easy

A. resource { prevent_destroy = true }

B. prevent_destroy = true

C. lifecycle { prevent_destroy = true }

D. lifecycle { prevent_delete = true }

Solution

1. Step 1: Identify correct syntax for lifecycle block

   The prevent_destroy must be inside a lifecycle block within the resource.

2. Step 2: Check option correctness

   lifecycle { prevent_destroy = true } correctly places prevent_destroy = true inside lifecycle { }. Others are either missing the block or have wrong keywords.

3. Final Answer:

   lifecycle { prevent_destroy = true } -> Option C

4. Quick Check:

   Correct lifecycle syntax = C [OK]

Hint: Always put prevent_destroy inside lifecycle block [OK]

Common Mistakes:

• Placing prevent_destroy outside lifecycle block
• Using wrong keyword like prevent_delete
• Adding prevent_destroy directly under resource

3. Given this Terraform resource snippet, what happens if you run terraform destroy?

resource "aws_s3_bucket" "example" {
  bucket = "my-bucket"
  lifecycle {
    prevent_destroy = true
  }
}

medium

A. Terraform will show an error and stop the destroy

B. Terraform will delete the S3 bucket without error

C. Terraform will ignore prevent_destroy and delete anyway

D. Terraform will update the bucket instead of deleting

Solution

1. Step 1: Understand prevent_destroy effect on destroy

   The prevent_destroy = true stops Terraform from deleting the resource during destroy.

2. Step 2: Predict Terraform behavior on destroy

   Terraform will detect the rule and raise an error, preventing the deletion.

3. Final Answer:

   Terraform will show an error and stop the destroy -> Option A

4. Quick Check:

   prevent_destroy blocks destroy = A [OK]

Hint: prevent_destroy causes destroy to error, not delete [OK]

Common Mistakes:

• Assuming resource deletes anyway
• Thinking it updates instead of blocking destroy
• Believing Terraform silently ignores the rule

4. You added prevent_destroy = true to a resource but now need to delete it. What is the correct way to fix the error during terraform destroy?

medium

A. Run terraform destroy with --force flag

B. Remove or comment out the prevent_destroy line and apply again

C. prevent_destroy = false

D. Delete the resource manually from the cloud console

Solution

1. Step 1: Understand how prevent_destroy blocks deletion

   The rule must be removed or disabled in Terraform code before deletion can proceed.

2. Step 2: Identify correct fix

   Removing or commenting out the line and applying changes allows Terraform to delete the resource safely.

3. Final Answer:

   Remove or comment out the prevent_destroy line and apply again -> Option B

4. Quick Check:

   Disable prevent_destroy before destroy = B [OK]

Hint: Disable prevent_destroy in code before deleting resource [OK]

Common Mistakes:

• Using unsupported --force flag
• Setting prevent_destroy directly under resource
• Deleting resource manually without Terraform sync

5. You have a Terraform resource with prevent_destroy = true. You want to replace this resource safely without downtime. Which approach is best?

hard

A. Temporarily remove prevent_destroy, apply destroy, then recreate resource

B. Manually delete resource in cloud console, then run terraform apply

C. Use terraform taint to mark resource for replacement without removing prevent_destroy

D. Set prevent_destroy to false and run terraform apply to replace resource

Solution

1. Step 1: Understand prevent_destroy blocks deletion

   Removing prevent_destroy allows deletion but risks downtime; manual deletion is unsafe.

2. Step 2: Disable prevent_destroy for safe replacement

   Setting prevent_destroy = false inside the lifecycle block disables the deletion block. Then terraform apply can replace the resource if config changes require recreation.

3. Step 3: Apply changes safely

   This triggers replacement using Terraform's logic (e.g., with create_before_destroy if set), avoiding manual steps.

4. Final Answer:

   Set prevent_destroy to false and run terraform apply to replace resource -> Option D

5. Quick Check:

   Set prevent_destroy = false allows replacement = C [OK]

Hint: Set prevent_destroy = false before terraform apply to replace [OK]

Common Mistakes:

• Using `terraform taint` without disabling prevent_destroy
• Manually deleting resource causing drift
• Running destroy separately, risking downtime