Code review for infrastructure changes in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of a code review in infrastructure changes?

To ensure the infrastructure code is correct, secure, and follows best practices before deployment.

beginner

Name one key aspect to check during a Terraform code review.

Check that resource naming is consistent and meaningful to avoid confusion.

intermediate

Why should you review Terraform state file changes during a code review?

To verify that the planned infrastructure changes match the intended updates and avoid accidental deletions or modifications.

beginner

What is a common security check in infrastructure code reviews?

Ensure no sensitive data like passwords or keys are hardcoded in the code.

intermediate

How can peer reviews improve infrastructure code quality?

They catch errors early, share knowledge, and enforce standards, leading to safer and more reliable infrastructure.

What should you verify first in a Terraform code review?

A The color scheme of the code editor

B The planned changes match the intended infrastructure updates

C The number of comments in the code

D The size of the Terraform binary

The main goal is to ensure the planned changes align with what is intended to avoid mistakes.

Which of the following is a bad practice in infrastructure code?

A Hardcoding passwords directly in the code

B Writing clear resource names

C Using variables for sensitive data

D Adding comments to explain complex parts

Hardcoding sensitive data can lead to security risks and should be avoided.

During a code review, why is it important to check resource dependencies?

A To make the code look cleaner

B To reduce the number of lines of code

C To ensure resources are created in the correct order

D To increase the size of the state file

Correct dependencies ensure infrastructure components are created or destroyed in the right sequence.

What tool can help visualize Terraform plan changes during review?

A Terraform plan output

B Text editor themes

C Browser bookmarks

D Operating system logs

Terraform plan shows the proposed changes and helps reviewers understand what will happen.

Which practice improves collaboration in infrastructure code reviews?

A Deploying without review

B Ignoring comments from reviewers

C Skipping tests before merging

D Using pull requests for changes

Pull requests allow team members to review and discuss changes before applying them.

Explain the key steps you take when reviewing Terraform infrastructure code changes.

Think about what you want to see before applying changes to real infrastructure.

Describe why code reviews are important for infrastructure as code and how they help prevent problems.

Consider the risks of deploying infrastructure without review.