Auto-approve flag and its danger in Terraform - Step-by-Step Execution

Process Flow - Auto-approve flag and its danger

Start terraform apply

↓

Check auto-approve flag

↓

Skip prompt

↓

Apply changes

↓

Finish

↓

Finish

Terraform apply checks if auto-approve is set. If yes, it skips confirmation and applies changes immediately. If no, it asks for user confirmation before applying.

Execution Sample

Terraform

terraform apply -auto-approve

# Applies changes without asking for confirmation

This command runs terraform apply and skips the confirmation prompt, applying changes immediately.

Process Table

Step	Auto-approve Flag	User Prompt	Action Taken	Result
1	Yes	Skipped	Apply changes immediately	Infrastructure updated without confirmation
2	No	Shown	Wait for user input	User confirms or cancels
3	No	User confirms	Apply changes	Infrastructure updated after confirmation
4	No	User cancels	Abort apply	No changes made

💡 Execution stops after changes are applied or user cancels.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
auto_approve	unset	true	false	false	false
user_prompt	unset	skipped	shown	shown	shown
apply_action	none	applied	waiting	applied	aborted
infrastructure_state	unchanged	updated	unchanged	updated	unchanged

Key Moments - 2 Insights

Why is skipping the confirmation prompt dangerous?

Because changes are applied immediately without user review, mistakes or unintended changes can happen, as shown in step 1 of the execution_table.

What happens if the user cancels when auto-approve is not set?

The apply is aborted and no changes are made, as shown in step 4 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the action taken when auto-approve is set to Yes?

A Abort apply

B Wait for user confirmation

C Apply changes immediately

D Show error

💡 Hint

Refer to step 1 in the execution_table where auto-approve is Yes.

At which step does the user have a chance to cancel the apply?

A Step 1

B Step 4

C Step 2

D Step 3

💡 Hint

Look at the execution_table rows where user cancels the apply.

If auto-approve is false, what variable tracks whether the user prompt is shown?

A user_prompt

B apply_action

C auto_approve

D infrastructure_state

💡 Hint

Check variable_tracker for user_prompt values when auto_approve is false.

Concept Snapshot

terraform apply -auto-approve skips confirmation prompt
Danger: changes apply immediately without review
Without auto-approve, user must confirm before apply
Use auto-approve carefully to avoid unintended changes
Best practice: avoid auto-approve in production

Full Transcript

When you run terraform apply, it usually asks you to confirm before making changes. If you add the -auto-approve flag, it skips this confirmation and applies changes right away. This can be dangerous because you might apply changes you did not intend. Without auto-approve, Terraform waits for your confirmation, and you can cancel if needed. The key variables are auto_approve which controls skipping prompt, user_prompt which tracks if confirmation is shown, apply_action which shows if changes are applied or aborted, and infrastructure_state which shows if infrastructure is updated. Always be careful using auto-approve to avoid mistakes.