choudoufu

choudoufu

Per-resource locking for OpenTofu.

choudoufu is a build of OpenTofu. `choudoufu live-check` tells you offline whether your configuration runs as it is. In place of one lock on the whole state, it keeps one record per resource and writes an ownership marker on each cloud object, so two applies of saved plans that change different resources run at the same time. The state file becomes a copy you can rebuild.

The engine terragucci can run, with binary: choudoufu. It uses chant's ownership markers, and chant can run it.

Where to start

• OpenTofu or Terraform on your own backend
• Starting fresh

First command

Needs: The GitHub CLI, signed in.

os=$(uname -s | tr '[:upper:]' '[:lower:]')
arch=$(uname -m | sed 's/x86_64/amd64/; s/aarch64/arm64/')
gh release download -R INTENTIUS/choudoufu --pattern "*_${os}_${arch}.tar.gz"
tar xzf choudoufu_*_"${os}"_"${arch}".tar.gz

The full steps

DocsSourceEvidence

You run todayOpenTofu or TerraformWith a state fileTerragrunt or AtmosRoots with their own stateterraguccichoudoufu as its binaryNothing yetA new estate

Runs onAWSTags and IAM conditionsKubernetesLabels and admissionGCPLabels and project IAMAzureTags and resource groups

Migrate an existing estate

Then read From a state file and On AWS.

Differs

• The live backend, in estate.chdf.hcl, takes the place of the backend block.
• Run live-import before the first apply, so every resource carries its marker.

Or start from your roleI review security or own accessI am evaluatingI drive a coding agentI want to contribute