cub changeworkflow delete

Delete a change workflow or multiple change workflows

Synopsis

Delete a change workflow or multiple change workflows using bulk operations.

A change order that named the workflow keeps the annotation naming it, so deleting a workflow a rollout is still moving under leaves that rollout with nothing to advance through. Abort the change order, or keep the workflow until it is done.

Single change workflow delete:

  cub changeworkflow delete --space workflows myapp-main-line

Bulk delete with --where:

Delete multiple change workflows at once based on search criteria.

Examples:

  # Delete the workflows of a retired component's spaces
  COMPONENT_ID=$(cub component get legacy-app -o jq=.Component.ComponentID)
  cub changeworkflow delete --where "Space.ComponentID = '$COMPONENT_ID'"

  # Delete specific change workflows by slug
  cub changeworkflow delete --changeworkflow old-main-line,deprecated-main-line

cub changeworkflow delete [<slug or id>] [flags]

Options

      --changeworkflow strings        target specific change workflows by slug or UUID for bulk delete (can be repeated or comma-separated)
      --filter string                 Filter entity to apply to the list. Specify as 'space/filter' for cross-space filters or just 'filter' for current space. Supports both slugs and UUIDs. The filter will be combined with any --where clause using AND logic. Examples: "production-filters/security-check", "my-filter-uuid", "validation-rules"
      --from-backing-units            prune: delete only the changeworkflows selected whose backing Units are empty, which says they should not exist, and keep the Units; the rest are left alone
  -h, --help                          help for delete
      --include-hidden string[="*"]   Also select hidden entities, to list or to act on: those hidden for the given HiddenReasons, comma-separated, as in --include-hidden=BackingUnit, or for any reason when given no value or "*". ConfigHub/YAML Units, which hold the configuration of other entities, are hidden with the reason BackingUnit. A --where naming entities by Slug or ID selects them whether hidden or not
  -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
      --where string                  Filter expression using SQL-inspired syntax. Supports conjunctions with AND. String operators: =, !=, <, >, <=, >=, LIKE, NOT LIKE, ILIKE, ~~, !~~, ~, ~*, !~, !~*. Pattern matching with LIKE/ILIKE uses % and _ wildcards. Regex operators (~, ~*, !~, !~*) support POSIX regular expressions. A related entity is referenced by prefix, as in "UpstreamUnit.Slug = 'base'"; when the reference names a list, a * segment matches any element, as in "FromLink.*.Slug = 'upgrade-app'". Examples: "Slug LIKE 'app-%'", "DisplayName ILIKE '%backend%'", "Slug ~ '^[a-z]+-[0-9]+$'". 'cub <entity> explain --where' lists the attributes an entity's expressions can name

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>; "*" 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

cub changeworkflow delete