stado service handoff-release-control
Invocation
stado service handoff-release-control [OPTIONS] --host <HOST> --product <PRODUCT> <SERVICE>Purpose
Hand a placed logical service's lifecycle to its active signed release. The release must already be committed and ready, and the legacy unit must already be inactive. One conditional registry write then removes every legacy restart identity while preserving the logical route, placement dependency, probes, and release policy. Repeating an incomplete handoff rechecks the same release, rollout generation and exact legacy files before committing against the current registry. The prior commit remains in the receipt's recovery history. A completed receipt cannot be reapplied against a mismatching registry.
Required inputs and options
| Input or option | Contract |
|---|---|
<SERVICE> | Logical service in the service directory and placement profile |
--host <HOST> | Active registry host serving the release-controlled stable bind |
--product <PRODUCT> | Exact product in registry.release_control |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.