-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Addition of "--quiet" flag Where Applicable #11515
Comments
The --quiet option usually stops progress output. But for those tools that do not currently have --quiet, I have no problem with that change. I am not sure it is customary to block stderr on --quiet though. |
Personally I have seen behavior vary between tools. Perhaps --quiet by default could only block stdout while something like --quiet=stderr or --quiet=both would also block stderr. |
That is a difficult change, since --quiet is a boolean, Getting CLI Processor to handle something like that would be difficult. |
Of course if it prohibitively difficult just stopping output to stdout will suffice. However having both would be nice to have. |
A friendly reminder that this issue had no activity for 30 days. |
Fixes: containers#11515 Signed-off-by: Daniel J Walsh <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
Would it be possible to add a --quiet flag to various commands that would prevent any output to stdout? For example both
podman stop
andpodman rm
would be good candidates. Of course one can always&> /dev/null
but there are instances where that is not available i.e running podman without using a shell.The text was updated successfully, but these errors were encountered: