stado placement standby
Invocation
stado placement standby [OPTIONS] --host <HOST> --reason <REASON> <PROFILE>Purpose
Make a registered host a place this profile may move to: deliver each service's program (a managed program now; a release-controlled tree through the host's own agent), stage each unit rendered from the service catalog where the move starts it (installed, not loaded, not declared), and write the host into the profile and the directory once every unit is staged. Idempotent; a unit already running on the host is refused as a second active copy, and a pass that stops at a pending rollout says so and the next pass continues
Required inputs and options
| Input or option | Contract |
|---|---|
<PROFILE> | The placement profile to prepare the host for |
--host <HOST> | Registered host that must stand by for it |
--reason <REASON> | Why this host must stand by for the profile |
--json | Emit the receipt as JSON |
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
- Registered host that must stand by for it
- Why this host must stand by for the profile
- 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.