Plan Once, Apply the Same Plan: A Terraform Pipeline with OIDC and an Approval Gate
A Terraform pipeline with OIDC credentials, per-environment runners and a saved plan that is exactly what a human approves and what gets applied.
Architecture, cloud, and software engineering insights
⚠️ Blog posts are currently written in a single language.
A Terraform pipeline with OIDC credentials, per-environment runners and a saved plan that is exactly what a human approves and what gets applied.
Following a correlation header through a Node proxy, PHP middleware and Go services, and the PSR-7 detail that quietly dropped the ID on the way down.
Two generations of Go web libraries: recovering panics once, giving callers a quotable reference, and the context mistake that silently empties it.
A /health that always returns 200 stays green while the database is down. Liveness versus readiness, and a small Go pattern for checks that tell the truth.
Config templates in one repo, rendered by a config service at container start, with an entrypoint that refuses to boot without them. Why, and where it bites.