Skip to content

cub worker update

cub worker update

Update a bridge worker or multiple bridge workers

Synopsis

Update a bridge worker or multiple bridge workers using bulk operations.

Single bridge worker update:

  cub worker update --space my-space my-worker

Bulk update with --patch:

Update multiple bridge workers at once based on search criteria. Requires --patch flag with no positional arguments.

Examples:

  # Update all bridge workers with specific labels using JSON patch
  echo '{"Labels": {"env": "prod"}}' | cub worker update --patch --where "Labels.tier = 'backend'" --from-stdin

  # Update specific bridge workers by slug
  cub worker update --patch --worker my-worker,another-worker --from-stdin < patch.json
cub worker update [<name>] [flags]

Options

      --annotation strings    annotations in key=value format; can separate by commas and/or use multiple instances of the flag
      --delete-gate strings   delete gates in key[=true] format; can separate by commas and/or use multiple instances of the flag
      --filename string       Read the ConfigHub entity JSON from file, URL (https://), or stdin (-); mutually exclusive with --from-stdin
      --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-stdin            Read the ConfigHub entity JSON (e.g., retrieved with cub <entity> get --quiet --json) from stdin; merged with command arguments on create, and merged with command arguments and existing entity on update
  -h, --help                  help for update
      --label strings         labels in key=value format; can separate by commas and/or use multiple instances of the flag
      --org-role string       organization-level role for the worker (e.g., admin, manager, editor, user, viewer, creator, member, none)
  -o, --output string         Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
      --patch                 use patch API for individual or bulk operations
      --permission strings    permission in format Action:UserIDOrUsername to add, or -Action:UserIDOrUsername to remove (e.g., Manage:user@example.com, -View:user@example.com, can be repeated)
      --quiet                 No default output.
      --replace               Replace entity instead of merging when using --from-stdin or --filename
      --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. Examples: "Slug LIKE 'app-%'", "DisplayName ILIKE '%backend%'", "Slug ~ '^[a-z]+-[0-9]+$'"
      --worker strings        target specific bridge workers by slug or UUID for bulk patch (can be repeated or comma-separated)

Options inherited from parent commands

      --context string   The context to use for this command
      --debug            Debug output
      --space string     space ID to perform command on

SEE ALSO