Use it#
The pages a reader needs once they are past the model and the policies: what a real config runs into, how to bring an existing estate in or start a new one, and day-to-day operation. Where things are stored and the fork’s own surface are here too.
| Page | Question it answers |
|---|---|
| Compatibility reference | What in a real configuration this fork accepts or refuses |
| Resource tier lookup | Your resource types, one by one: tier, status, and why for anything not admitted yet |
| How to check a configuration before migrating | Running choudoufu live-check against your own code |
| What you set up by hand | What must exist before the first run, versus what the tool creates |
| Migrate an existing estate | How resources you already manage bind to their markers |
| Day-2 operations | Renaming, removing, recording effects and working with other people, indexed |
| Start a new estate | The live block, from a first apply |
| Questions | Short answers to the questions that come up first |
| How to write markers inside a for_each’d module | Threading each.key through a wrapped module by hand |
| Where things are stored | State, records and receipts, and what lives where |
| How the compatibility numbers are measured | Where the corpus ranking comes from, and what not to read into it |
| How the pinned AWS provider gets bumped | What a provider upgrade can change, and how it is reviewed |
| Running an estate from CI | The five jobs a choudoufu pipeline runs, per forge, and what the governance policies lock |
| Reference | The fork’s call surface, per stage |