cub changeset move

Move changesets to another space

Synopsis

Move changesets to another space.

A changeset keeps its identity: everything that uses it refers to it by ID and keeps using it. Moving requires Manage permission on each changeset and CreateChildren permission on the destination space.

A changeset's start and end tags move with it. Its revisions and units stay where they are.

Every check runs over the whole selection before anything moves, so a move that would collide with a name in the destination moves nothing. Rename first if a name is taken; --dry-run reports what a move would do.

Examples:

  # Move one changeset
  cub changeset move --space my-space my-changeset other-space

  # Move every changeset with a label
  cub changeset move --space my-space --where "Labels.team = 'web'" other-space

  # Preview a move across all spaces
  cub changeset move --where "Labels.team = 'web'" --dry-run other-space

  # Move specific changesets by slug
  cub changeset move --space my-space --changeset my-changeset,another-changeset other-space

cub changeset move [<changeset-slug>] <to-space> [flags]

Options

      --changeset strings             move specific changesets by slug or UUID (can be repeated or comma-separated)
      --dry-run                       report what the move would do without moving anything
      --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 move
      --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.
      --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

      --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>

cub changeset move