Terraform modules.
Terraform modules are reusable, versioned units of infrastructure definition. Instead of every environment declaring resources from scratch, a module encapsulates a pattern — a network, a database, a service — and each caller supplies inputs.
Where Terraform modules fits on a long engagement.
The reason to modularise is that environments diverge otherwise. Staging and production declared independently will differ within months, in ways nobody documented, and the first time that matters is when something works in one and not the other. A module makes the shared shape explicit and the differences a short list of inputs.
Two things cause most Terraform pain, and neither is the language. State is the real artefact — if it is lost or corrupted, Terraform no longer knows what it manages — so remote state with locking is not optional. And drift, where someone changes a resource in the console, means the code no longer describes reality; detecting it needs a scheduled plan rather than trust.
What an assigned team does with Terraform modules.
Infrastructure code is written once and read for years, usually under pressure by whoever is on call. Clarity is worth more than cleverness here, because the audience is a tired person at 3am rather than a reviewer at their desk.
That audience is also the reason continuity matters so much on platform work: the person who wrote it being reachable is often the difference between a short incident and a long one. How that responsibility is held is set out in how an assignment runs.
What we use Terraform modules for.
- Environments that genuinely match Staging and production from one module, so a difference is a declared input rather than a surprise.
- Drift detected rather than discovered A scheduled plan that reports console changes before they cause an incident.
- A reviewed pattern for new services Network, permissions and monitoring included by default, instead of reassembled each time.
How Terraform modules capacity is assigned.
Infrastructure capacity is assigned under devops as a service, with state management and drift detection treated as part of the work rather than assumed.
Tell us what your roadmap needs Terraform modules for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.