cub changeworkflow
cub changeworkflow
ChangeWorkflow commands
Synopsis
The changeworkflow subcommands manage ChangeWorkflows.
A ChangeWorkflow declares how a change is promoted: the ordered stages it moves through, which Spaces each stage selects, and the gates that have to pass before it enters one. It is the definition; a ChangeOrder is the invocation, and one workflow governs many of them.
A workflow names no base Space and no scope. Both come from the ChangeOrder being promoted -- the base is the Space the change order lives in, and a stage's Spaces are those its WhereSpace selects among the change order's InScopeSpaceIDs -- so one workflow resolves to different Spaces under different change orders. That is what lets a workflow be cloned into another component's Space and give it the same shape of rollout, which "cub changeworkflow create" does in bulk mode.
The component plays no part in which Spaces a stage selects. The Component named by the ComponentID of the change order's Space decides only which workflows it may be promoted under, with its AllowedChangeWorkflowIDs and ChangeWorkflowRequired.
"cub changeorder create --change-workflow" names the workflow a change order is promoted under.
A workflow with no stages governs ChangeSets rather than ChangeOrders: its Final prerequisites must hold in every Space the ChangeSet was opened in for the ChangeSet to close. "cub changeset create --change-workflow" names the workflow a ChangeSet is governed by.
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 changeworkflow
--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
- cub - ConfigHub CLI
- cub changeworkflow create - Create a new change workflow or bulk create change workflows
- cub changeworkflow delete - Delete a change workflow or multiple change workflows
- cub changeworkflow edit - Edit a change workflow in your system's editor
- cub changeworkflow explain - Explain ChangeWorkflow fields from the OpenAPI spec
- cub changeworkflow get - Get details about a change workflow
- cub changeworkflow list - List change workflows
- cub changeworkflow move - Move changeworkflows to another space
- cub changeworkflow rename - Rename a changeworkflow
- cub changeworkflow update - Update a change workflow or multiple change workflows