Skip to content

cub channel move

cub channel move

Move channels to another space

Synopsis

Move channels to another space.

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

Its command runs move with it. A channel a client holds the lease of is not moved: stop the client first.

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 channel
  cub channel move --space my-space my-channel other-space

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

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

  # Move specific channels by slug
  cub channel move --space my-space --channel my-channel,another-channel other-space

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

Options

      --channel strings               move specific channels 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

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