docs(pipectl): correct the deploy-collapse design before it is built #2020

Merged

sean merged 1 commit from docs/r10-correction into trunk 2026-08-07 19:33:33 +00:00

Conversation 0 Commits 1 Files changed 1 +37 -11

sean commented 2026-08-07 19:33:01 +00:00

Owner

Copy link

R10 as planned would have inferred promote/rollback from cluster state. That contradicts the invariant that a Deployment NAMES its Release and Target when created — spec.operation is declared, write-once intent with CEL coupling to retryOf.

Corrected: one deploy verb with --as promote|rollback and --retry-of. Nothing inferred.

Also records R9 done.

R10 as planned would have inferred promote/rollback from cluster state. That contradicts the invariant that a Deployment NAMES its Release and Target when created — spec.operation is declared, write-once intent with CEL coupling to retryOf. Corrected: one deploy verb with --as promote|rollback and --retry-of. Nothing inferred. Also records R9 done.

sean added 1 commit 2026-08-07 19:33:01 +00:00

docs(pipectl): correct the deploy-collapse design before it is built ... 8daedb56cd

R10 as planned would have had the DeploySubmitter infer promote or rollback from
the relationship between a version and a target.

That contradicts a hard invariant this repository already states: a Deployment
names its Release and Target when created, and does not discover them from
workflow output, naming conventions, or current cluster state. spec.operation is
declared, write-once intent, and CEL already couples it to retryOf. Inferring it
would replace a recorded decision with a guess, and the guess would be wrong
exactly when it matters -- a re-deploy of an older version is a rollback only if
somebody meant it as one.

The corrected collapse keeps the declaration and drops only the verbs: one
deploy verb with --as promote|rollback and --retry-of. Nothing is inferred.

Also records that R9 is done.

sean merged commit 8daedb56cd into trunk 2026-08-07 19:33:33 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

sean/pipelines!2020

No description provided.