stado release catalog declare-publisher
Invocation
stado release catalog declare-publisher [OPTIONS] --owner <OWNER> --client <CLIENT> <PRODUCT>Purpose
Declare one product's release publisher across the fleet: mint its item on the vault owner, grant the release client access, declare it on every participating host, then reconcile each host's verifier grant. `build submit` and `release submit` run this themselves for a product this host has not declared, with this host as the client and the vault owner read from `skarbiec bond status`; run it by hand only to declare further API targets or reloads
Required inputs and options
| Input or option | Contract |
|---|---|
<PRODUCT> | The product, as its release manifest names it |
--owner <OWNER> | The registry host whose vault is authoritative |
--client <CLIENT> | The registry host that runs `release submit` |
--target <TARGETS> | Further hosts that serve the release API; repeat for several |
--reload <RELOADS> | HOST=SERVICE: the host Stado process on HOST, whose release API caches the publisher table for its lifetime, reconciled after the declaration lands on that host; repeat for several hosts. Any other unit, a retired one included, is refused |
--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
- Any other unit, a retired one included, is refused
- 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.