oz0 hub
A plugin hub, such as the orchestrator-zero/hub repository, keeps one listing file per plugin, listings/<publisher>/<plugin>.yaml, and builds a signed index from them.
For: Operators and developers looking up a command.
A plugin hub, such as the orchestrator-zero/hub repository, keeps one listing file per plugin, listings/<publisher>/<plugin>.yaml, and builds a signed index from them.
Authors write only the source, the versions, the maintainers, the tags and the homepage, issues and security links; the hub computes the Repository link from the verified source, and the README in the package is the plugin's documentation; everything about what the plugin contains and may do comes from plugin inspect of the pinned source, which the hub's CI runs again with its own pinned engine.
Usage
oz0 hub [command]
Subcommands
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.