cub trigger update

Update a trigger or multiple triggers

Synopsis

Update a trigger or multiple triggers using bulk operations.

Single trigger update:

Function arguments can be provided as positional arguments or as named arguments using --argumentname=value syntax. Once a named argument is used, all subsequent arguments must be named. Use "--" to separate command flags from function arguments when using named function arguments.

Example with named arguments:

  cub trigger update --space my-space my-trigger Mutation Kubernetes/YAML -- set-annotation --key=cloned --value=true

Bulk update with --patch:

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

Examples:

  # Disable all triggers for a specific function
  cub trigger update --patch --where "FunctionName = 'cel-validate'" --disable

  # Enable all disabled triggers
  cub trigger update --patch --where "Disabled = true" --enable

  # Update worker for all triggers of a certain type using JSON patch
  echo '{"BridgeWorkerID": "worker-uuid"}' | cub trigger update --patch --where "ToolchainType = 'Kubernetes/YAML'" --from-stdin

  # Mark triggers as warn mode
  cub trigger update --patch --where "Event = 'Mutation'" --warn

  # Update specific triggers by slug
  cub trigger update --patch --trigger my-trigger,another-trigger --disable

cub trigger update [<slug or id>] [<event> <config type> <function> [<arg1> ...]] [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
      --description string         description explaining the trigger's purpose and how to fix failures
      --disable                    Disable trigger
      --enable                     Enable trigger (use with --patch for bulk)
      --fail-open-after string     duration after which disconnected worker triggers fail open (e.g., 6h, 30m)
      --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
      --invocation string          invocation to execute (alternative to specifying function and arguments)
      --label strings              labels in key=value format; can separate by commas and/or use multiple instances of the flag
      --other-data-source string   source of additional data to pass to the function (e.g., LiveRevisionNum)
  -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
      --quiet                      No default output.
      --replace                    Replace entity instead of merging when using --from-stdin or --filename
      --trigger strings            target specific triggers by slug or UUID for bulk patch (can be repeated or comma-separated)
      --unit-filter string         filter entity (slug or UUID) to restrict which Units this trigger applies to
      --unwarn                     Set trigger to produce ApplyGates (default, use with --patch for bulk)
      --verbose                    Detailed output, additive with default output
      --warn                       Set trigger to produce ApplyWarnings instead of ApplyGates
      --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]+$'"
      --where-resource string      metadata path expression to restrict which resources the trigger operates on
      --where-unit string          filter expression to restrict which Units this trigger applies to
      --worker string              worker to execute the trigger function

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

cub trigger update