Skip to content
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

Closed
p0da opened this issue Sep 9, 2021 · 5 comments · Fixed by #12151
Closed

[Feature Request] Addition of "--quiet" flag Where Applicable #11515

p0da opened this issue Sep 9, 2021 · 5 comments · Fixed by #12151
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@p0da
Copy link

p0da commented Sep 9, 2021

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 and podman 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.

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 9, 2021
@rhatdan
Copy link
Member

rhatdan commented Sep 9, 2021

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.

@p0da
Copy link
Author

p0da commented Sep 10, 2021

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.

@rhatdan
Copy link
Member

rhatdan commented Sep 17, 2021

That is a difficult change, since --quiet is a boolean, Getting CLI Processor to handle something like that would be difficult.

@p0da
Copy link
Author

p0da commented Sep 29, 2021

Of course if it prohibitively difficult just stopping output to stdout will suffice. However having both would be nice to have.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants