Most organizations treat their platform like a necessary evil, but that's exactly why they can't move fast when it matters most.
If you work in software and aren't spending $10/month on OSS, you're taking for granted the foundation your entire career is built on.
Blocking infrastructure drift with RBAC alone will just frustrate your engineer; here's how to make IaC changes so easy they'll actually want to use it.
How AI is going to change, but not replace, IaC.
What would a single-instance root module setup look like for a decent sized infra repo?
We worked with a client whose root Terraform module had 40,000 resources and took an hour to plan.
A story of a client who had Terraform here, CDK there, and manual management for their prod db.
Learn about a framework agnostic way to manage your TF backend in TF.
Spoiler: it was harder than they thought.
Using trunk, a megalinter, lets us lint our TF code, generate doc and more.
You know what is a serious pain? Getting ClickOps resources to be managed with IaC.
IaC code can either use inheritance or composition to add functionality. Which is the better path?