Skip to main content
Version: v5.6.1

opschain admin agent rollover continue

packs:agentspacks:agent-governance

opschain admin agent rollover continue <agent> [--lane <lane>] [--reason <text>] [--server <url>] [--auth-token <token>]

Release the rest of the lane after the canaries (v2 AgentService.AdvanceAgentRollover, action continue).

Applies to a canary rollover that is holding on its canaries: every remaining instance of the lane is drained and instructed to restart from the target release, and the rollover completes as they re-enrol. Lands info:agent:rollover_continued. Refused by name on any other state.

Under blue-green it applies to a rollover holding green_ready and is the flip: the green lane is re-verified at its size (refused green_not_ready with the counts otherwise), then the two lanes swap labels in one set-based write — the green instances take the serving lane's label and every new dispatch, the old instances take the green lane's name and serve nothing while their in-flight work finishes (flipped, info:agent:rollover_flipped).

Every step is attested on the release (opschain admin agent-release show) under the rollover's one correlation chain. <agent> is the agent's member id, <project>/<code>, or a bare code when exactly one project holds it; --lane names the lane whose open rollover the verb applies to.

Flags​

FlagMeaning
--lane <lane>The lane whose open rollover the verb applies to (default stable).
--reason <text>Audited reason.
--server <url>Server base URL. Default: the active context, then OPSCHAIN_SERVER.
--auth-token <token>Admin bearer token override. Default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login for that server.

Output​

rollover 01a1aecc-… of limebank/felix lane stable: continued (felix@2.0.0 → felix@2.1.0)

-o json|yaml prints the rollover document; the status becomes continued.

Exit codes​

CodeMeaning
0The verb applied.
1The server refused it: no rollover is open on the lane, or the rollover is not in a state the verb applies to (the message names the state).
2Usage — wrong arguments, or no server / admin token resolvable.

See also​

  • opschain docs cli/admin-agent-rollover — the rollover verb and its strategies.