cub review-comment create
cub review-comment create
Create a review comment
Synopsis
Create a review comment on a revision of a unit.
The comment can be about one resource, named as
Examples:
# Comment on revision 4 of a unit
cub review-comment create my-space/my-deployment --revision-num 4 --text "Why 5 replicas?"
# Comment on one path of one resource
cub review-comment create my-space/my-deployment --revision-num 4 \
--resource apps/v1/Deployment:default/web --path spec.replicas --text "Why 5 replicas?"
# Reply to a comment
cub review-comment create my-space/my-deployment --revision-num 4 \
--reply-to 61f26b06-3c34-4363-8b9d-7d0a7c2b5f1c --text "Load test results; see the change description."
cub review-comment create <unit> [flags]
Options
--dry-run report what the command would write, and write nothing
--filename string Read the ConfigHub entity's fields, as YAML or JSON, from file, URL (https://), or stdin (-), as --from-stdin does; mutually exclusive with --from-stdin
--from-stdin Read the ConfigHub entity's fields, as YAML or JSON, from stdin; merged with command arguments on create, and merged with command arguments and existing entity on update. A field the entity does not have, or one only the server sets, is refused; cub <entity> explain lists the fields
-h, --help help for create
-o, --output string Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
--path string path, within the resource, the comment is about
--quiet No default output.
--reply-to string ID of the review comment, on the same unit, this one replies to
--resource string resource the comment is about, as <resource-type>:<resource-name>, e.g. apps/v1/Deployment:default/web
--revision-num int number of the revision the comment is about (required)
--text string text of the comment (required)
--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>
--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 review-comment - Review comment commands