Repository navigation
Run a Move in the Release Gate and record it in ClusterState #336
Description
Parent
What
Teach the Release Gate to run a Move and record it (chapter 55). This is work in the gate's own repository (JorisJonkers-dev/delivery) and in the Collector's:
- start the step Jobs in order and hold on any failure; on a failure or an expired
delivery.move.timeoutafter the fence, unfence the source, flip any Stable Address back and hold the release; - after the flip, watch every Application with a required edge to the provider and raise an urgent report for one whose readiness does not return within its gate deadline;
- record the Move's phase and
flippedAtin the gate's record; the Collector reads them into ClusterState'sinstances.
Related: #240 (naming a release's steps in the releaseGate element, so the gate infers none).
Blocked by
#341, the map whose rewrite plan replaces the closed placement ticket #328 (see #350), and #335 (the Jobs the gate starts).
Activity
ExtraToast commentedon Oct 27, 2026
A contract for this ticket from #334 (PR #650), recorded in chapter 55. The Release Gate keeps
targetandflippedAton an Instance's ClusterState record after the source retires, until the old Project stops declaring the Application.Composition reads that record to tell a leftover declaration, which renders nothing, from a new Move. If the gate drops those fields at retirement, an old Project that still declares the Application looks like a fresh two-Project declaration again.
ExtraToast commentedon Nov 2, 2026
Closing as not planned: the maintainer decided (2026-11-02) to remove the Move from the model now that every Project is on the estate path. The Move existed only to carry data across the migration off the previous delivery path. The removal is tracked in #807.