Use it
| Getting started | |
|---|---|
| Will my configuration work? | What is accepted and what is refused, in one table |
| Check a configuration | choudoufu live-check on your own code, before anything runs |
| What you set up by hand | What must exist before the first run |
| Start a new estate | From nothing to a first apply |
| Migrate an existing estate | Bringing in resources you already manage |
| Day to day | |
|---|---|
| Day-2 operations | Rename, remove, receipts, working with other people |
| Recover an estate | What to do when the cache or the record store is gone |
| Running an estate from CI | The five jobs a pipeline runs |
| Reading a value from another estate | A data source on the live resource |
| The record store | |
|---|---|
| Where things are stored | Markers, records, receipts and the cache |
| Set up a record store bucket | The bucket, its three settings, and the policy for an estate’s role |
| Secrets in the record store | Who can read an estate’s recorded values |
| Look it up | |
|---|---|
| Reference | The live block, the commands, and the permissions a run needs |
| Resource tier lookup | Every resource type, and what recovers its identity |
| The ownership policy matrix | What a plan does with a marked or unmarked resource |
| Scoping a role | IAM policies on the marker |
| Questions | Short answers |
- Scoping a role
- Resource tier lookup
- Will my configuration work?
- How to check a configuration before migrating
- What you set up by hand
- Migrate an existing estate
- Day-2 operations
- Recover an estate
- How to rename a resource
- Start a new estate
- Questions
- How to stop managing or destroy a resource
- How to write markers inside a for_each'd module
- Receipts: make an external effect show up in a plan
- Where things are stored
- Reading a value from another estate
- Secrets in the record store
- Set up a record store bucket
- The ownership policy matrix
- Reference
- Running an estate from CI