oz0 plugin push
For: Operators and developers looking up a command.
Publish a bundle (or a folder, packed first) to an OCI registry as an artifact of type application/vnd.oz0.plugin.v1: a config with the plugin's name and version (application/vnd.oz0.plugin.config.v1+json) and the bundle as its one layer (application/vnd.oz0.plugin.bundle.v1.tar+gzip). It prints the manifest's digest, which is what plugin install oci://...@sha256:<digest> takes: plugins install from registries by digest only, never by a tag that can move. The same bundle always gives the same digest.
Credentials come from --username with --password-stdin, or OZ0_REGISTRY_AUTH (user:password); registries on this machine are reached over plain HTTP (servers do that only in dev mode). This runs on your machine; servers pull with a tenant secret.
Usage
oz0 plugin push <bundle|dir> oci://<registry>/<repository>[:<tag>] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--json | bool | print JSON instead of a table | |
--password-stdin | bool | read the registry password or token from stdin | |
--username | string | the registry user |
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.