cub run patch-mutations
cub run patch-mutations
Selectively patch attributes if their mutations indicate they are patchable. Intended to be used with compute-mutations. Mutating. Supported toolchains: AppConfig/Env, AppConfig/INI, AppConfig/JSON, AppConfig/Properties, AppConfig/TOML, AppConfig/Text, AppConfig/YAML, ConfigHub/YAML, Kubernetes/YAML
cub run patch-mutations [flags]
Options
--clearance string The classes of reason this operation is cleared for, as a JSON Clearance. An absent or empty clearance clears nothing, so every guarded path is withheld.
-h, --help help for patch-mutations
--mutation-patch string (required) Mutations to filter and patch
--mutation-protection string (required) The target's MutationSources, whose Protected flags say which paths the patch may not overwrite
--mutations-to-subtract string Mutations to subtract from the patch (e.g., target-side changes relative to a merge base) before applying. Pass an empty list or omit to skip subtraction.
--path-annotations string The target's PathAnnotations, whose guards say which paths this operation must be cleared for before it may write them. Pass an empty list or omit when the target has none, which costs nothing.
Options inherited from parent commands
--change-desc string change description
--changeset string changeset to associate units with
--context string The context to use for this command
--debug Debug output
--dry-run dry run mode: execute functions but skip updating configuration data
--executor-space string Space ID or slug whose executor to use for builtin functions (org-level only)
--filter string filter to apply (slug, space/filter, or UUID)
--guard stringArray reason to record on the paths this change writes, as KEY=VALUE (repeatable). A later operation must be cleared for it before overwriting those paths. Adds and overwrites only; retiring a guard is cub unit set-guard --remove-guard
-o, --output string Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
--protect record the paths this change writes as protected local overrides, so a later merge from upstream does not overwrite them; by default a change claims nothing and each path keeps the protection it already has
--quiet No output
--resource-type string resource-type filter
--show string Select which part of the function response to display. One of: output, values, data
--space string space ID to perform command on
--toolchain string Toolchain type for the function invocations (default "Kubernetes/YAML")
--unit strings target specific units by slug or UUID (can be repeated or comma-separated)
--wait wait for completion
--where string where filter
--where-data string where data filter
--where-resource string filter which resources the function operates on
--worker string worker to execute the function
SEE ALSO
- cub run - invoke a function