Practice English vocabulary for collaborating on infrastructure code: PR reviews, plan output as PR comments, production approvals, and team IaC module ownership.
0 / 5 completed
1 / 5
What does 'the PR reviews the infrastructure change' mean?
Treating IaC like application code means infrastructure changes are proposed as pull requests, reviewed by peers, and only merged after approval. This catches mistakes, shares knowledge, and creates an audit trail of every infrastructure change.
2 / 5
What does 'the terraform plan output is posted as a PR comment' mean?
Tools like Atlantis, Terraform Cloud, or GitHub Actions workflows automatically run 'terraform plan' and post the diff as a PR comment. Reviewers see the exact additions, changes, and deletions before approving, making reviews meaningful rather than just code inspection.
3 / 5
What does 'the change requires a second approver for production' mean?
Four-eyes principles (two-person approval) for production IaC changes reduce the risk of mistakes. Tools like Atlantis enforce approval policies: for example, prod workspace changes require two approvals while dev workspace changes may only need one.
4 / 5
What does 'the infrastructure code review vocabulary' include?
Reviewing IaC requires specific vocabulary to discuss plans and changes: reviewers comment on plan output interpretation, resource lifecycle changes (create/update/replace/destroy), module versions, variable validation, and compliance with organizational standards.
5 / 5
What does 'the team owns the IaC modules' mean?
In large organizations, platform or infrastructure teams own shared IaC modules (e.g., a VPC module, an RDS module). They act as the maintainers, versioning releases, handling breaking changes, and providing support to consumer teams.