Stategraph

I ran `terraform plan` against the multiverse. Not metaphorically. Literally. I built a provider that manages every cloud resource in every dimension. The plan took 11 years because the state file was a pickle. So we replaced it with a graph. Now I can see which resources depend on which across 6,000 realities. One of those realities is run entirely by sentient YAML. They were not happy about the indentation. Not my problem. Stategraph Demo Day, November 4. Show up or don't. You've already registered in 3 of your timelines. https://lnkd.in/e49ewTXE #terraform #AmIOkIDontKnow

Terragrunt was a brilliant fix in 2016, and it’s a little sad we’re all still stuck there. https://lnkd.in/e49ewTXE #terraform

You only need one Terraform state file. Every state file past the first is a workaround. You probably didn't split because you wanted to. Terraform made you do it. One file, one lock, every plan refreshes everything. So everyone agreed that hundreds of tiny states wired together with remote state lookups is an architecture. Impossible to manage at scale. Every split is a boundary a plan can't see across, and a change that crosses it is two applies. When the second one fails, you're half deployed. Stategraph stores state in Postgres as a graph. A plan covers what a change reaches. A lock covers what a change touches. State size stops mattering, so there's nothing left to split for. Demo Day, November 4, 18:00 CET, 12:00 ET, 9:00 PT. https://lnkd.in/e49ewTXE #terraform

Terragrunt is a band-aid. It stitches together the structure Terraform never gave you. But each fix is another unit, another state file, another plan built on mock values. On Nov 4, Josh Pollara and Malcolm will show the cross-state fix underneath, live.

How much of your week is Terraform planning? Josh Pollara and Malcolm will show a no-op plan that used to take 3 hours finish in 97 seconds. Same state. Same change. Live Nov 4.

Terragrunt `mock_outputs` is like skydiving without a parachute. When the VPC hasn't been applied yet, the unit that depends on it plans against values you made up. vpc_id = "mock-vpc-id". That is the plan your reviewer approves. That is the artifact your entire change process rests on. A plan is supposed to be a statement of truth about what is going to happen. A plan computed from fiction is not a plan. It's a lie. Stategraph plans the VPC and the database together, against the real graph. One plan. One apply. Sweet mustache though! #terraform