cub release
cub release
Release commands
Synopsis
The release subcommands publish, list, get, update, withdraw, and delete releases.
A release bundles the configuration of the Units in a Space that are assigned to a
given Target, captured at a point in time, and serves it as an OCI bundle. Releases
are created with cub release publish, taken out of service with
cub release withdraw, and removed with cub release delete;
their bundled content is read-only throughout. cub release update changes
a release's labels, annotations and delete gates -- but never what it bundles, nor
the name the bundle is stored under.
Options
--component string the Component of --variant, when that names the variant alone; --variant <component>/<variant> says the same in one flag
-h, --help help for release
--space string space to operate in, by slug or UUID. Omitted, a list or bulk operation spans the organization and a single entity is named as <space>/<slug>
--variant string variant to operate in, as <component>/<variant>, or as <variant> with --component: the space naming that Component whose Variant label is <variant>. The same scope as --space, named by what it is rather than by the space's slug; the two cannot be combined
Options inherited from parent commands
--context string The context to use for this command
--debug Debug output
SEE ALSO
- cub - ConfigHub CLI
- cub release delete - Delete a release
- cub release explain - Explain Release fields from the OpenAPI spec
- cub release get - Get details about a release
- cub release list - List releases
- cub release publish - Publish a release
- cub release update - Update a release
- cub release withdraw - Withdraw a release