Stacks on plunge
llms.txtlists every page for an agent
Who it is for
You run plunge (the Pulumi fork from the team behind plywood) or plan to.
Features
- A plunge+ backend URL runs every stage with plunge
- Two merged pull requests on separate resources of one stack update at once, since nothing locks the stack
- A saved plan carries the version of each record it read, and up refuses a record that moved
- plunge drift checks a single resource against the cloud
Every setup gets
- One preview note on every pull request
- Updates of the previews you approved
- No overlapping or stale updates
- Re-preview from a comment
- Scheduled drift checks
- Separate identities to preview and to update
- Policy on every preview, CrossGuard included
- An audit trail in your own repository
- Secrets stay [secret] in notes
- Your backend and your runners, as they are
Differences
- plunge keeps no stack history; bucket versioning keeps earlier versions of each record.
First step
Then read
- How-to
- Explanation
- Locking and staleness
- Reference
- StagesExit codes