Auto-approve flag and its danger in Terraform - Commands & Configuration

Introduction

Terraform helps you create and change cloud resources safely. The auto-approve flag lets you skip the manual approval step when applying changes. This can speed up automation but can also cause unexpected changes without review.

When you want to automate Terraform apply in a script or CI/CD pipeline without manual intervention

When you are confident about the changes and want to save time by skipping the approval prompt

When running quick tests in a disposable environment where manual approval is unnecessary

When you want to avoid blocking automation workflows that require Terraform apply

When you want to reduce human error by automating the entire apply process

Commands

This command plans and applies infrastructure changes but asks for your approval before making any changes.

Terminal

terraform apply

Expected Output

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create



Terraform will perform the following actions:



  + aws_instance.example



Plan: 1 to add, 0 to change, 0 to destroy.



Do you want to perform these actions?  Terraform will perform the actions described above.

  Only 'yes' will be accepted to approve.



  Enter a value: 

This command applies changes immediately without asking for your approval, speeding up automation but risking unintended changes.

Terminal

terraform apply -auto-approve

Expected Output

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create



Terraform will perform the following actions:



  + aws_instance.example



Plan: 1 to add, 0 to change, 0 to destroy.



aws_instance.example: Creating...

aws_instance.example: Creation complete after 10s [id=i-1234567890abcdef0]



Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

→

-auto-approve - Skips the interactive approval prompt and applies changes immediately

Key Concept

If you remember nothing else from this pattern, remember: using auto-approve skips your chance to review changes and can cause unexpected or harmful infrastructure updates.

Common Mistakes

Using terraform apply -auto-approve without reviewing the plan first

This can cause unintended changes or deletions in your infrastructure without warning.

Always run terraform plan first to review changes before using auto-approve to apply them.

Using auto-approve in production environments without safeguards

It removes the manual checkpoint that helps prevent mistakes in critical systems.

Avoid auto-approve in production or combine it with automated checks and approvals.

Summary

terraform apply runs the plan and waits for your approval before making changes.

Adding -auto-approve skips the approval prompt and applies changes immediately.

Using auto-approve can speed up automation but risks applying unintended changes without review.

Practice

1. What does the -auto-approve flag do when running terraform apply?

easy

A. It cancels the apply process automatically.

B. It shows a detailed plan before applying changes.

C. It skips the confirmation prompt and applies changes immediately.

D. It only validates the configuration without applying changes.

Solution

1. Step 1: Understand the purpose of the -auto-approve flag

   This flag is designed to skip the manual confirmation step during terraform apply.

2. Step 2: Identify the effect on the apply process

   By skipping confirmation, Terraform applies changes immediately without waiting for user input.

3. Final Answer:

   It skips the confirmation prompt and applies changes immediately. -> Option C

4. Quick Check:

   -auto-approve skips confirmation [OK]

Hint: Remember: auto-approve means no manual confirmation [OK]

Common Mistakes:

• Thinking it shows the plan before applying
• Assuming it cancels the apply
• Confusing it with validation only

2. Which is the correct syntax to apply Terraform changes without confirmation?

easy

A. terraform apply --force-apply

B. terraform apply --skip-confirm

C. terraform apply --no-approve

D. terraform apply -auto-approve

Solution

1. Step 1: Recall the exact flag name for skipping confirmation

   The correct flag is -auto-approve, which tells Terraform to apply changes without asking.

2. Step 2: Check the options for correct syntax

   Only terraform apply -auto-approve uses the correct flag -auto-approve with proper syntax.

3. Final Answer:

   terraform apply -auto-approve -> Option D

4. Quick Check:

   Correct flag syntax is -auto-approve [OK]

Hint: Flag always spelled exactly as -auto-approve [OK]

Common Mistakes:

• Using --skip-confirm which does not exist
• Confusing with --no-approve or --force-apply
• Adding extra dashes or misspelling the flag

3. Given this command: terraform apply -auto-approve, what is the main risk involved?

medium

A. Changes will be applied without reviewing the plan first.

B. Terraform will only validate the configuration.

C. Terraform will prompt twice for confirmation.

D. Terraform will not apply any changes.

Solution

1. Step 1: Understand what -auto-approve does

   This flag skips the manual confirmation step, so Terraform applies changes immediately.

2. Step 2: Identify the risk of skipping confirmation

   Without reviewing the plan, unintended or harmful changes might be applied automatically.

3. Final Answer:

   Changes will be applied without reviewing the plan first. -> Option A

4. Quick Check:

   Auto-approve skips review, causing risk [OK]

Hint: Auto-approve skips review, so risk is blind apply [OK]

Common Mistakes:

• Thinking no changes will apply
• Assuming double confirmation happens
• Believing it only validates without applying

4. You ran terraform apply -auto-approve and accidentally deleted a critical resource. What is the best way to prevent this in the future?

medium

A. Always run terraform apply without any flags.

B. Use -auto-approve only after reviewing the plan with terraform plan.

C. Disable Terraform state locking.

D. Run terraform apply -auto-approve twice to confirm.

Solution

1. Step 1: Identify the cause of accidental deletion

   Using -auto-approve without reviewing the plan can cause unintended changes.

2. Step 2: Find the best practice to avoid mistakes

   Always review the plan output with terraform plan before applying changes automatically.

3. Final Answer:

   Use -auto-approve only after reviewing the plan with terraform plan. -> Option B

4. Quick Check:

   Review plan before auto-approve prevents mistakes [OK]

Hint: Review plan first, then auto-approve safely [OK]

Common Mistakes:

• Thinking running apply without flags always prevents errors
• Disabling state locking which is unrelated
• Running auto-approve twice does not add confirmation

5. In an automated CI/CD pipeline, you want to safely use terraform apply -auto-approve. Which practice reduces the danger of unintended changes?

hard

A. Run terraform plan and save the plan output, then apply only if the plan matches expectations.

B. Use -auto-approve with terraform destroy to clean up resources automatically.

C. Skip the plan step and apply directly to save time.

D. Run terraform apply manually after the pipeline finishes.

Solution

1. Step 1: Understand the risk of auto-approve in automation

   Auto-approve skips manual review, so unintended changes can happen if the plan is not checked.

2. Step 2: Identify a safe automation practice

   Running terraform plan first and saving its output allows verification before applying changes automatically.

3. Step 3: Confirm the best option

   Run terraform plan and save the plan output, then apply only if the plan matches expectations. describes this safe practice, reducing risk in CI/CD pipelines.

4. Final Answer:

   Run terraform plan and save the plan output, then apply only if the plan matches expectations. -> Option A

5. Quick Check:

   Plan then apply ensures safe automation [OK]

Hint: Always plan and verify before auto-approve in pipelines [OK]

Common Mistakes:

• Skipping plan to save time
• Using auto-approve with destroy carelessly
• Running apply manually defeats automation purpose