Writing merge-friendly Terraform modules
Large plans scare reviewers because risk hides between benign lines. We coach learners to structure modules around clear inputs, explicit defaults, and narrow outputs so diffs read like memos instead of novels.
Naming conventions matter less than predictable file boundaries. We show how to isolate environment wiring from shared service definitions, then attach policy tests that fail fast when someone sneaks a broad IAM action into a shared module.
We also cover how to pair plans with short human narratives: what will change, what will not, and which rollbacks were rehearsed. That habit transfers directly to operational reviews in enterprise markets.
The capstone expects a recorded walkthrough of a plan/apply cycle with a deliberate rollback. Mentors grade clarity, not line count—verbosity is treated as a smell.