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

Print a warning when an ignored option is used #7960

Closed
2 tasks
jamest-gaia opened this issue Jun 9, 2023 · 2 comments
Closed
2 tasks

Print a warning when an ignored option is used #7960

jamest-gaia opened this issue Jun 9, 2023 · 2 comments
Assignees
Labels
duplicate This issue is a duplicate. feature-request A feature should be added or improved. s3

Comments

@jamest-gaia
Copy link

jamest-gaia commented Jun 9, 2023

Describe the feature

Print a warning to the operator when receiving an option that is ignored.
E.g.

$ aws s3 ls --output json
**ignoring option --output, see aws s3 ls help` for more info**
2020-12-21 14:58:42 mybucket-name
2021-04-14 13:55:06 mybucket2-name
etc..

Use Case

I need this feature because I was frustrated trying to get json output from the aws s3 ls command using the documented --output option. I only became aware it was not supported after searching and finding #709

Proposed Solution

If I use an option that is ignored such as --output on aws s3 please print a warning to let me know that.

Other Information

See #709

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CLI version used

2.11.26

Environment details (OS name and version, etc.)

Linux/5.10.16.3-microsoft-standard-WSL2 exe/x86_64.debian.11

@jamest-gaia jamest-gaia added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Jun 9, 2023
@tim-finnigan tim-finnigan self-assigned this Jun 9, 2023
@tim-finnigan
Copy link
Contributor

Thanks @jamest-gaia for reaching out. I understand your frustration about the --output command being ignored in this scenario. I recently opened a related issue here to document this inconsistency: #7634. Because these issues call out the same underlying problem, I think we should consolidate them for tracking purposes. But I will reference your suggestion to add a warning in that issue.

@tim-finnigan tim-finnigan added duplicate This issue is a duplicate. s3 and removed needs-triage This issue or PR still needs to be triaged. labels Jun 9, 2023
@github-actions
Copy link

github-actions bot commented Jun 9, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue is a duplicate. feature-request A feature should be added or improved. s3
Projects
None yet
Development

No branches or pull requests

2 participants