cub unit data-edit
cub unit data-edit
Edit the config data of a unit in your system's editor
Synopsis
Open the config data of a unit, as 'cub unit data' shows it, in the editor named by the EDITOR environment variable, or vi if it is not set. When the editor exits, the changes are saved as a new revision. If the data was not changed, no update is made.
A guarded path the edit changes is written only if --clearance covers its guards. The edit is saved without the changes it does not cover, and those are listed as conflicts, which 'cub unit conflicts --apply' applies.
cub unit data-edit <unit> [flags]
Options
--changeset string changeset to associate the unit with
--clearance stringArray class of guarded reason this change is cleared for, as KEY, KEY=VALUE[;VALUE...], KEY!=VALUE[;VALUE...], or !KEY to refuse any path carrying KEY (repeatable). A guarded path this does not cover is not written, and the withheld change is reported as a conflict
-h, --help help for data-edit
--timeout string completion timeout as a duration with units, such as 10s or 2m (default "10m0s")
--wait wait for completion (default true)
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
- cub unit - Unit commands