Closed yobyot closed 4 years ago
Hello, thanks for reaching out. Now that we are shaping the new modular AWS Tools for PowerShell we are even more interested in user feedback.
Get-AWSCmdletName
to get the list of all cmdlets from imported AWS.Tools modules (we are planning to extend this to include cmdlets from AWS.Tools modules that are not imported or installed). You can also use Get-Command -Module AWS.Tools.*
for a list of all cmdlets from installed modules.Thanks again for the feedback!
Hello, thanks for opening this issue. We have created the AWS.Tools.Installer module to simplify installation, uninstallation and update of the AWS.Tools.Module.
The next release of AWS.Tool will also include a Get-AWSService cmdlet allowing to list the available modules.
Get-AWSService is now available in AWS Tools for PowerShell version 4. AWS.Tools.Installer is also available for use in production environments.
Breaking up the monolithic cmdlet modules has some negative impacts on usability.
First, there's the problem of synching .Common with everything else, as described in #38.
Beyond that, there are additional issues I hope you can address over time.
Install-Module [some includes-all-modules-name
to install all the modules. Many DevOps like me don't care about having all the modules available -- I don't know what I am going to want when. I also work on multiple machines and keeping track of which module is installed where is complicated when they are in little(r) pieces.While I appreciate that the
AWSPowerShell.NetCore
had grown too large for you, decomposing it makes additional work for some users like me who had grown used to getting everything at once. In my world, waiting five seconds for the fat boy to load into memory is worth the wait because it was convenient.AWS.Tools.* may be svelte but skinny ain't everything. :-)