CLI reference / product / registry / add

stado product registry add

Invocation

stado product registry add [OPTIONS] --name <name> --owner-repository <owner-repository> --description <description> --visibility <visibility> --family <family> --status <status> --id <id>

Purpose

Register one product

Required inputs and options

Input or optionContract
--catalog <catalog>Independent authoritative catalog path
--name <name>Product display name
--owner-repository <owner-repository>Canonical GitHub owner/repository
--workspace <workspace>The workspace of canonical checkouts this operation reads and builds from; default WISENT_WORKSPACE, else ~/Documents/CodingProjects/Wisent
--description <description>What the product does
--visibility <visibility>Product visibility: public or private
--family <family>Product family
--status <status>Product lifecycle status
--evidence <evidence>Canonical source reference; repeatable
--surface <surface>Surface declaration KIND=OWNER/REPOSITORY; repeatable
--installation <installation>Installation declaration; repeatable
--integration <integration>Directional product integration; repeatable
--service-file <service-file>Service declaration YAML or JSON file
--approved-by <approved-by>Actual operator who approved this product
--approval-note <approval-note>Recorded approval provenance
--jsonPrint the registry mutation and persisted record
--id <id>New product identifier

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.