Repository navigation
Add a Converge button to the service page - #8
Merged
Merged
Conversation
The daemon has accepted POST /services/{name}/converge since v0.1.8, but the
page offered no way to press it, so operators first-started born-managed
services from the devtools console. The button opens a confirmation that
states what converge does (re-render from the merged manifest, restart, no
automatic rollback), POSTs with no body over the same forward-auth session as
Deploy, and follows the run through the same refresh and event stream. A 202
that joined an already-pending converge keeps the dialog open to say so;
a refusal lands in the dialog and the banner.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the web UI half of converge that the 2026-08-27 design left out of scope.
api.converge(service)POSTs to/api/v1/services/{name}/convergewith no body and no header of its own (same-origin, forward-auth session, like Deploy).postnow returns the daemon's full{journalId, joined}.ConvergeConfirmdialog: states converge re-renders the unit from the merged manifest and restarts it with no automatic rollback, shows the pin main holds now, and notes the daemon re-syncs at the front of the queue.lastDeploy.joined: truekeeps the dialog open with a notice naming the pending run; an error lands in the dialog and the banner.Tests:
api.test.ts(route, no body, no headers, escaping, fresh/joined/missing-joined 202, JSON and non-JSON errors, deploy body unchanged) andstate.test.ts(joinedNotice, converge history row).web/distrebuilt.Verified in a browser against a scratch mock daemon: joined notice, 400 surfaced in dialog + banner, fresh 202 closed the dialog and the rail followed the streamed
reconcilingevent.