stado service release
Invocation
stado service release [OPTIONS] --host <HOST> --product <PRODUCT> --version <VERSION> <NAME>Purpose
Install and activate one service release, rolling back on failed readiness
Required inputs and options
| Input or option | Contract |
|---|---|
<NAME> | Service name as the registry manages it |
--host <HOST> | Command option; required or optional as shown in the invocation. |
--product <PRODUCT> | Product in registry.release_control |
--version <VERSION> | Exact desired semantic version to activate |
--readiness-url <READINESS_URL> | Optional loopback HTTP endpoint that must answer after restart |
--readiness-timeout-seconds <READINESS_TIMEOUT_SECONDS> | Maximum seconds to wait for readiness [default: 30] |
--reload-unit | Reload a system LaunchDaemon's unit definition before readiness. `kickstart` reuses launchd's cached ProgramArguments. Use this when the plist was repointed from a legacy path to managed `current`. |
--require-release-version | Require readiness JSON field `releaseVersion` or `build.version` to equal `--version` |
--supersede-unit <SUPERSEDE_UNIT> | Replace one legacy user LaunchAgent atomically with this release. The legacy unit is restored when activation fails. Its plist is deleted only after exact readiness passes. |
--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
- Optional loopback HTTP endpoint that must answer after restart
- Require readiness JSON field `releaseVersion` or `build.version` to equal `--version`
- 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.