Skip to content

cub changeset delete

cub changeset delete

Delete a changeset or multiple changesets

Synopsis

Delete a changeset or multiple changesets using bulk operations.

Single changeset delete: 

  cub changeset delete my-changeset

Bulk delete with --where:

Delete multiple changesets at once based on search criteria.

Examples: 

  # Delete all changesets created before a specific date
  cub changeset delete --space my-space --where "CreatedAt < '2024-01-01'"

  # Delete changesets with specific descriptions
  cub changeset delete --space my-space --where "Description LIKE '%deprecated%'"

  # Delete changesets across the organization: without --space, --where spans every space
  cub changeset delete --where "Labels.cleanup = 'true'"

  # Delete specific changesets by slug
  cub changeset delete --changeset old-changeset,deprecated-changeset

A change set is not deleted while revisions or units outside the delete are in it, or its tags mark revisions there. The error names them. Pass --detach to take them out of the change set as part of the delete: 

  cub changeset delete --detach my-changeset

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

Options

      --changeset strings             target specific changesets by slug or UUID for bulk delete (can be repeated or comma-separated)
      --detach                        Remove the references other entities have to what is deleted, instead of refusing the delete while any remain
      --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"
  -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]+$'"

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

SEE ALSO