cub release delete
cub release delete
Delete a release
Synopsis
Delete a release, identified by its globally-unique release ID.
Deletion removes the release and its stored bundle. To take a release out of
service while retaining it, use cub release withdraw instead.
The release is located by its ID regardless of which Space it lives in, so --space is not required (a Release lives in its bundled Units' Space, which need not be the caller's default).
Examples:
cub release delete 61f26b06-3c34-4363-8b9d-7d0a7c2b5f1c
A release is not deleted while it, or the tag it made, marks revisions. The error names them. Pass --detach to remove those marks as part of the delete; the tag it made is deleted with it:
cub release delete --detach 61f26b06-3c34-4363-8b9d-7d0a7c2b5f1c
cub release delete <release-id> [flags]
Options
--detach Remove the references other entities have to what is deleted, instead of refusing the delete while any remain
-h, --help help for delete
-o, --output string Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
--quiet No default output.
--verbose Detailed output, additive with default output
Options inherited from parent commands
--component string the Component of --variant, when that names the variant alone; --variant <component>/<variant> says the same in one flag
--context string The context to use for this command
--debug Debug output
--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
SEE ALSO
- cub release - Release commands