aws
Stable plugin API
Hello! It looks like someone opened a similar issue previously, but it was closed after an individual posted a sample of a plugin, and then got some assistance with troubleshooting. I wanted to open a new issue to focus on the OP's original question, which was -- is there a stable API (or is the current one stable) for creating AWS CLI plugins?
There's still a few larger issues we need to resolve before we're ready to open up plugins to the world (a sane distribution strategy, for instance). While I can't give a specific timeline, this is something we'd like to do sooner rather than later.
Isn't pip a good enough distribution strategy?
Can we at least get an enumeration of all the larger issues blocking this work?
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
Based on community feedback, we have decided to return feature requests to GitHub issues.
I came to this trying to understand how to use awscli-plugin-endpoint with awsv2 https://github.com/wbingli/awscli-plugin-endpoint/issues/15
I'm confused by the intent behind the documention for the "interm" cli_legacy_plugin_path support:
https://awscli.amazonaws.com/v2/documentation/api/latest/topic/config-vars.html#plugins
https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration-changes.html#cliv2-migration-profile-plugins
that path seems to be the path in the container - but so, how are you supposed to get the plugin in the container? Is there a documented path for that, or should users just expect to have to replace the amazon/aws-cli with a new image that has their plugin in it?
Would the team be open to plugin system PRs to introduce support for Using package metadata?
I've also found the plugin system logging happens before the --debug flag takes effect, so that may require some work too.
