Coordinating changes
Coordinating applies comes down to ownership and boundaries, and the way you implement them shapes every operation below.
Two changes to one resource
A backend lock keeps the state file consistent. A reviewed plan catches two people changing the same resource, in either model.
Two applies at once
A lock per backend makes runs in one estate take turns. A lock per resource lets runs on different resources go together.
Move a resource to another estate
Handing a resource to another owner means moving its state between backends, or editing one label.
An apply killed part way
A run that dies holds its backend's lock until someone clears it. With a lock per resource, the next run starts straight away.
Start a new estate
Under a backend per boundary, a new estate brings a new backend. Under labels, it joins the backend you already run.
choudoufu and the Terraform state file
Section titled “choudoufu and the Terraform state file”Same HCL, same providers, same plan. Everything else is stock OpenTofu.
Who can touch what
When something breaks
A crash, a killed job, a lost file.
Two changes at once
Where it runs
Sources read 2026-10-25. Terraform is a trademark of HashiCorp, an IBM Company. OpenTofu is a trademark of The Linux Foundation.
plunge and the Pulumi checkpoint
Section titled “plunge and the Pulumi checkpoint”Your Pulumi programs, SDKs and providers run unchanged.
Who can touch what
When something breaks
A crash, a killed run, a surprise delete.
Two changes at once
Where it runs
Pulumi and the Pulumi logo are trademarks of Pulumi Corporation, and plunge is independent of it.
Intentius builds behold, chant, choudoufu, plunge, plywood and terragucci. Everything is open source at github.com/intentius. Also from Intentius are blacklight, spicypath and the wardens GitHubGitLabForgejo.
The tools are free. For help with them, get in touch.
Intentius