generate-cli-skeleton argument would benefit all commands

[mdaniel]

I was unable to discern why the generatecliskeleton customization does not apply to all aws-cli sub-commands. I didn't know if it was an oversight, or if it was explicitly excluded from commands for a reason.

For example, one will observe that cloudformation get-template has both --generate-cli-skeleton and the consumer --cli-input-json, but emr create-cluster, on the other hand, does not honor it even though it has way more options and thus would benefit from it more.

Unless there is a reason, it would be absolutely great to have those two arguments accepted by all aws-cli commands, to reduce the amount of shell quoting and "pseudo DSL" use in the option parsing.

[cjpetrus]

+1 I really want this feature.

[R-Gerard]

+1

[dkmn]

+1

[sopel]

I also just stumbled over this unexpected asymmetry, specifically for the aws . lambda . invoke call, which seems particularly odd insofar all other aws . lambda commands (incl. the deprecated invoke-async) do support --generate-cli-skeleton and --cli-input-json just fine.

@mtdowling - it would be great to get a response from the AWS team concerning the blocking constraints, if any. Given quite some code is auto generated meanwhile, I wouldn't wanna dive into this until it has been confirmed to require manual efforts rather than tweaks to the code generation that is under stewardship of the AWS team. Thanks much!

[proinsias]

This would indeed greatly simplify automated generated of aws cli commands. Can we get an update from the maintainers?

[leonmax]

+1

[ASayre]

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

This entry can specifically be found on UserVoice at: https://aws.uservoice.com/forums/598381-aws-command-line-interface/suggestions/33168385-generate-cli-skeleton-argument-would-benefit-all-c

[jamesls]

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

[lokkju]

I'm particularly in need of --generate-cli-skeleton for the EMR create-cluster command; are there any plans to fix this?

[ChristopherHackett]

I was hoping to be able to regenerate a very old cluster that had run using the request parameters outputted by CloudTrail however I stumbled on emr create-cluster not supporting the feature.

Note: it appears EMR on EKS supports this so a little surprising the older more established EMR did not!