Skip to content

planguard: whether a plan may be applied unread - nothing, apply, or person - #123

Merged
aledbf merged 1 commit into
mainfrom
planguard
Nov 19, 2026
Merged

aledbf merged 1 commit into
mainfrom
planguard

Conversation

@aledbf

@aledbf aledbf commented Nov 19, 2026

Copy link
Copy Markdown
Member

spinbox.dev follows the edge channel and its module's main, and every release
and module commit was a plan somebody read and an apply somebody ran, for a
change nobody chose (spin-terraform-aws#130: 29 merges in 15 days, 7 of them a
release). planguard reads tofu show -json and says whether the plan only adds
and updates in place - applied on a schedule - or takes something away: a
delete, a replacement, a forget, an action it does not know, which a person
reads. The plan cannot say which resources hold data, so none is assumed not
to; a type named as made to be replaced may be, never deleted alone.

Checked: tests, lint, mutate (39 refused, 0 survived); on real OpenTofu 1.12.6 plans: creates → apply, a replacement → person (apply with -replaceable for its type), no changes → nothing.

For spinbox.dev-deploy's scheduled apply, the rest of spin-terraform-aws#130's part 4 and shipset#22.

🤖 Generated with Claude Code

…person

spinbox.dev follows the edge channel and its module's main, and every release
and module commit was a plan somebody read and an apply somebody ran, for a
change nobody chose (spin-terraform-aws#130: 29 merges in 15 days, 7 of them a
release). planguard reads `tofu show -json` and says whether the plan only adds
and updates in place - applied on a schedule - or takes something away: a
delete, a replacement, a forget, an action it does not know, which a person
reads. The plan cannot say which resources hold data, so none is assumed not
to; a type named as made to be replaced may be, never deleted alone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit ddbbe76 into main Nov 19, 2026
3 checks passed
@aledbf
aledbf deleted the planguard branch November 19, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant