cub unit mutation-sources

Show what set each value in a unit's config data

Synopsis

Display a unit's MutationSources: for each resource and each path within it, what set the value that is there.

MutationSources is not part of the Unit entity, so no form of 'cub unit get' returns it. Use -o json / -o yaml / -o jq= to shape the output; the payload is the list of resources, so a path is addressed as '.[0].PathMutationMap'.

For a single Unit's history, 'cub unit get -o mutations' shows the same information as a table.

With --where, reads every unit the clause selects in one request rather than one per unit. Each row carries the unit it belongs to, so the payload is addressed as '.[0].MutationSources' rather than '.[0]'. Scoped to --space unless that is "*". Examples:

cub unit mutation-sources --space my-space my-unit cub unit mutation-sources --space my-space --where "Slug LIKE 'app-%'"

cub unit mutation-sources <unit> [flags]

Options

  -h, --help                          help for mutation-sources
      --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.
      --select string                 Comma-separated list of fields to retrieve and display. Entity IDs and Slug are always included. Example: "DisplayName,CreatedAt,Labels"
      --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>
      --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

cub unit mutation-sources