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

Add a verbose flag to prevent the CLI to display additional information #340

Open
fharper opened this issue Sep 7, 2023 · 3 comments
Open

Comments

@fharper
Copy link

fharper commented Sep 7, 2023

When I use the command volume ls, even when I don't have dangling volumes, I always get the list, no matter the format, in addition to the Info: Volumes with status 'dangling' mean they are attached to a cluster that no longer exists. You can attach them to an instance, or delete them if they are no longer needed..

It's great when using the CLI, but it's the kind of information I do not want to display when using the CLI for some automation. It could be nice to have a --verbose flag with either different level of verbose or as a boolean, which would have true as default, and setting it to false wouldn't show that kind of information output for any commands (not sure which others commands display that additional information in addition to the normal command output).

Not critical, just a “nice to have" option.

@Sheikh-Abubaker
Copy link

Hi @fharper,

Where should I head to know more about this issue and how do I reproduce it ?

@fharper
Copy link
Author

fharper commented Sep 25, 2023

@Sheikh-Abubaker: use the volume ls command. I get this warning every time even if all my volumes have an attached status.

@fharper
Copy link
Author

fharper commented Nov 1, 2023

It can also be only omitted when using the --output flag since it's probably only while using a specific output for data manipulation that this additional information verbose is causing issue. I had to add an additional check before processing the data, not critical, but this option would be nice. I think it would even be better that way.

Let me know if there is a preferred way, I can submit a PR to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants