Skip to content

cub changeset

cub changeset

ChangeSet commands

Synopsis

The changeset subcommands are used to manage changesets.

A ChangeSet groups the revisions of a change across many units. Open one on units with 'cub variant changeset open' or 'cub unit update --patch --changeset ', and close it with 'cub variant changeset close' or 'cub unit update --patch --changeset -'. A ChangeSet created with --change-workflow closes only once that workflow's Final prerequisites hold; closing anyway takes --force-reason (with --force-close on cub unit update). The Revisions of a ChangeSet that has not closed cannot be released.

ChangeSets are explained at https://docs.confighub.com/background/entities/changeset/. A guide for how to use ChangeSets is at https://docs.confighub.com/guide/changes/.

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 changeset
      --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>; "*" means the same as omitting it
      --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