Loading
Loading
Cookies & privacy
We use a couple of functional cookies plus privacy-respecting analytics to understand how the site is used. No advertising, no selling your data. Privacy Policy.
Insights
Showing every note filed under this topic.
Engineering
Pulumi and CDKTF keep arriving with better tooling. Here's why Terraform still wins for most teams we work with.
Engineering
One giant state file is a single point of failure with a 40-minute plan. Here is how we split state without turning every deploy into a scavenger hunt.
Engineering
Most modules die not because the code is bad but because the interface was wrong on day one. Notes on inputs, versioning, and saying no.
Engineering
Drift is not a tooling problem, it is a process problem. How we detect it on a schedule and decide what is worth correcting.
Engineering
Policy-as-code goes wrong when it becomes a bottleneck nobody can explain. How we write guardrails teams do not route around.
Engineering
Importing real production infrastructure is mostly archaeology, not coding. Our process for adopting click-ops without an outage.
Engineering
Most Terraform tests assert that Terraform works, which it does. Where Terratest, plan checks, and native tests earn their keep.
Engineering
The account boundary and the state boundary are not the same line. How we lay out accounts and decide where to cut state.
Engineering
Terraform state stores values in plaintext, including the secret you thought you protected. How we keep secrets out of state in practice.