Feature Request: Control how verbose output is
See original GitHub issueAs described in https://groups.google.com/forum/#!searchin/got-your-back/verbose|sort:date/got-your-back/50TDppD3-5E/971Z6SwtFwAJ, it would be helpful to have optionally quieter output.
Full steps to reproduce the issue:
- Run GYB (especially as a cron job)
- See many lines showing all updates
Expected outcome (what are you trying to do?):
I’d like to optionally see less output. I’d think that a numeric --verbose=<#>
argument would cover what I’m thinking of. The levels that occur to me are:
- Silent except for fatal errors
- Warnings but no other information
- Everything from lower levels and statistics on completion of a step but not status messages during the step
- Everything from lower levels and status messages during the step (this is the current output)
- Everything from lower levels and the current output from
--debug
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Developers - Feature Request: Control how verbose output is -
Expected outcome (what are you trying to do?): I'd like to optionally see less output. I'd think that a numeric --verbose=<#> argument would...
Read more >Feature Request: command line control of output variable visibility ...
I'd like to control the verbosity of terraform in general, and output vars specifically (I'd also like some means of controlling the order...
Read more >#PSTip Taking control of verbose and debug output, part 1
When working with cmdlets enabling verbose or debug output is easy: these commands have common switch parameters that can be used to do...
Read more >Verbose output - HTTPie 3.2.1 (latest) docs
To see all the HTTP communication, i.e. the final request/response as well as any possible intermediary requests/responses, use the --all option. The ...
Read more >Verbose Mode Options - Intel
Verbose Mode Options. The Diagnostics Utility for Intel® oneAPI Toolkits has six verbosity levels to add more detail in the output of each ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi, any chance this could be picked up again? From the comments it sounds like the pull request is very close.
Sorry it’s taken me forever to take a look. In general it looks good. rewrite_line() was an attempt by me to let GYB “say” more while taking less space. However it clearly made a mess for scheduled jobs and it’s probably outlived it’s usefulness. I suggest we try just doing away with it and making all of those calls just call logging at an appropriate level instead.
Also, what was the reasoning behind making DEBUG the default level and logging most informative messages under that instead of INFO?