Skip to content

Refine help output for generic flags #6207

Open
@rm3l

Description

@rm3l
    Just a discussion (also applies to the `run-on` flag):

From the user perspective, now that these two flags are visible globally, can the odo help output provide more guidance by telling users which commands these flags can be used with? I understand this would mean maintaining these descriptions, but I think it would be helpful.
So I'd suggest something like:

	pflag.CommandLine.String(VarFileFlagName, "", "File containing variables to override Devfile variables. Usable with \"odo dev\" and \"odo deploy\" commands.")

What do you think?

Because currently, users have to explicitly run the command to see if the flag can be used or not, e.g.:

> odo init --var USER                                                             
 ✗  --var-file and --var flags are not supported for this command

Originally posted by @rm3l in #6201 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/UXIssues or PRs related to User Experiencelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/LowNice to have issue. It's not immediately on the project roadmap to get it done.

    Type

    No type

    Projects

    • Status

      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions