Skip to content

cub unit path

cub unit path

Show everything recorded about one field of a unit

Synopsis

Show everything ConfigHub records about one field of a unit's configuration: its value, whether it is protected, the guards and other annotations on it, the conflicts and link findings about it, whether a link needs or provides it, and every change from this unit out to where the value was set -- each with its whole mutation and revision rather than the one line 'cub unit blame' has room for.

Name the field by the REF 'cub unit blame' printed for it, or any unambiguous prefix of at least four characters of one, or by its path. A path that more than one resource has needs --resource. A path that holds other fields, such as a container, lists the fields under it with their REFs.

For each change it shows: - the mutation: the function and its arguments, the link with its update type and upstream unit, the trigger or invocation, the merge it was and the upstream revisions it took, or the revision a restore went back to - the revision: the operation that made it, its description, who made it with what client and when, and the ChangeSet, ChangeOrders, Releases and Tags it belongs to

--history adds every change this unit has recorded to the field, oldest first, rather than only the last. It reads the record of every revision of the unit.

-o json and -o yaml emit the whole report, with each change's Mutation and Revision as the API returns them.

Examples:

  # A field by the REF 'cub unit blame' printed for it
  cub unit path --space prod-app ui 070f84b

  # The same field by its path
  cub unit path --space prod-app ui spec.template.spec.containers.?name=ui.image

  # A path two resources share
  cub unit path --space prod-app ui metadata.name --resource Deployment/ui

  # Every change recorded to the field
  cub unit path --space prod-app ui 070f84b --history
cub unit path <unit> <ref|path> [flags]

Options

  -h, --help                 help for path
      --history              list every change this unit has recorded to the field, not only the last
      --no-upstream          report this unit's own record without following a merge to where the value was set
  -o, --output string        Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
      --quiet                No default output.
      --resource string      the resource the path is in, as <type>/<name> or <name>, when more than one has it
      --upstream-depth int   how many upstream units to follow before giving up (default 8)
      --verbose              Detailed output, additive with default output

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