knative
Introduce --debug and --verbose as global options
In what area(s)?
Describe the feature:
Debugging and verbose output should be treated in a consistent way over all commands. Currently, we have
kn plugin list --verboseas in #313 for printing out plugin configurationkn service describe --detailsas in #252 for showing additional service information--log-httpas a global option to track HTTP API communication coming in with #326
As there are supposed to be more such output modifying flags coming in over time, I suggest to use --debug and --verbose with categories to fine tune this:
- Adding
--debugfor very low-level information. Only useful for developer ofknitself - Adding a
--verboseoption for increasing the detail level of the information presented. Examples arekn service describe --verboseto add more details to a service (like the image digests, or all env vars/annotations/labels)kn plugin list --verboseto also print the plugin directories where plugins are looked upkn service create --debugto print also the HTTP headers
In order to tune debug and verbose output, I'd suggest to introduce categories:
--debug--> all debug info--debug=all--> all debug info--debug=http--> only http related debugging--verbose--> all verbose output--verbose=config--> config related information, too--verbose=config,details--> config information and details (made up here to show how to combine categories)
This suggestion would introduce exactly two options, --debug and --verbose (with the possible values shown in the help page). The alternative would be to have an extra option for every category like in --log-http, but this would blow up the help pages and UX surface considerably over time.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
Related to this issue
- #182 --
--quietis kind of the opposite of--verbose - #390 --
--log-httpshould be included as part of--debug=http