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

Support short form arguments for high level commands #1602

Closed
JordonPhillips opened this issue Oct 28, 2015 · 7 comments
Closed

Support short form arguments for high level commands #1602

JordonPhillips opened this issue Oct 28, 2015 · 7 comments
Labels
automation-exempt Issue will not be subject to stale-bot feature-request A feature should be added or improved.

Comments

@JordonPhillips
Copy link
Member

For instance, instead of aws s3 sync --quiet ... we would have aws s3 sync -q.

We wouldn't be able to support these for every argument (sync, for instance, has five arguments that start with 'c'), but we could potentially cut down on some of the verbosity.

@JordonPhillips JordonPhillips added the feature-request A feature should be added or improved. label Oct 28, 2015
@rayluo
Copy link
Contributor

rayluo commented Nov 12, 2015

I can not speak for others. But personally I am not a big fan of this one. Because when there are common prefix, it would become another mental burden to remember "whether -q stands for --quiet or --query?", AND THEN if you would need to rely on searching another document for that answer, it counteracts the benefit of saving several key strokes.

Currently I'm using the auto-completion solution. It works quite well for me.

Just my $0.02 💰

@ASayre
Copy link
Contributor

ASayre commented Feb 6, 2018

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team

@ASayre ASayre closed this as completed Feb 6, 2018
@salmanwaheed
Copy link

salmanwaheed commented Feb 6, 2018 via email

@salmanwaheed
Copy link

salmanwaheed commented Feb 6, 2018 via email

@jamesls jamesls reopened this Apr 6, 2018
@jamesls
Copy link
Member

jamesls commented Apr 6, 2018

Based on community feedback, we have decided to return feature requests to GitHub issues.

@kdaily kdaily added the automation-exempt Issue will not be subject to stale-bot label Jul 29, 2020
@tim-finnigan
Copy link
Contributor

This issue hasn't received any 👍 reactions or community comments since being opened in 2015 so I think it should be closed. In addition to the command completion alternative mentioned earlier, another option is the auto-prompt mode in the AWS CLI v2.

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

⚠️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
automation-exempt Issue will not be subject to stale-bot feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

7 participants