Auto-approve flag and its danger in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the -auto-approve flag do in Terraform?

The -auto-approve flag skips the manual approval step and applies changes immediately without asking for confirmation.

beginner

Why can using -auto-approve be dangerous?

Because it applies changes without review, it can cause unintended infrastructure changes or outages if mistakes are present in the configuration.

beginner

What is a safer alternative to using -auto-approve?

Review the plan output manually and run terraform apply without -auto-approve to confirm changes before applying.

intermediate

In what situations might -auto-approve be acceptable?

In automated pipelines where changes are small, tested, and reviewed beforehand, and quick deployment is needed without manual steps.

intermediate

How can teams reduce risks when using -auto-approve in Terraform?

By implementing code reviews, automated tests, and approval gates before the apply step, even if -auto-approve is used in automation.

What happens when you run terraform apply -auto-approve?

A Terraform only shows the plan but does not apply changes.

B Terraform applies changes immediately without asking for confirmation.

C Terraform asks twice for confirmation before applying.

D Terraform cancels the apply process.

The -auto-approve flag skips the confirmation prompt and applies changes right away.

Why is it risky to use -auto-approve in production environments?

A It requires manual approval every time.

B It slows down the deployment process.

C It disables Terraform logging.

D It can cause unexpected infrastructure changes without review.

Using -auto-approve skips manual review, increasing the risk of mistakes affecting production.

Which practice helps reduce risks when using -auto-approve?

A Running automated tests and code reviews before apply.

B Skipping the plan step entirely.

C Applying changes without any prior checks.

D Using <code>-auto-approve</code> only on local machines.

Automated tests and code reviews catch errors before changes are applied automatically.

When might using -auto-approve be acceptable?

A In automated pipelines with tested and reviewed changes.

B When making large untested changes in production.

C When you want to avoid writing Terraform plans.

D When you want to disable Terraform state locking.

Automated pipelines with prior testing and review can safely use -auto-approve for faster deployment.

What does Terraform normally do before applying changes without -auto-approve?

A Skips the plan step.

B Applies changes immediately.

C Shows a plan and asks for manual confirmation.

D Deletes the state file.

Terraform shows the planned changes and waits for user confirmation before applying.

Explain what the -auto-approve flag does in Terraform and why it can be dangerous.

Think about what happens when you don't get a chance to review changes.

Describe best practices to safely use -auto-approve in automated Terraform workflows.

Consider how teams can prevent mistakes before applying changes automatically.