AWS.Tools.Installer module should check for updates and provide a warning with suggested update command. #321
Labels
feature-request
A feature should be added or improved.
module/powershell-cmdlets
p2
This is a standard priority issue
queued
xs
Effort estimation: tiny
Describe the feature
Due, I assume, to circular dependency issues, the
AWS.Tools.Installer
module does not update itself unlike all otherAWS.Tools.*
modules. However, there is no indication that your module is out of date unless you check the PSGallery or run commands such asFind-Module
,Update-Module
, etc. I believe we should implement a check insideInstall-AWSToolsModule
andUpdate-AWSToolsModule
that will check for a new version of the module when run, and if one is found, output a warning message suggesting an update and how it can be updated (viaInstall-Module -Name AWS.Tools.Installer -Scope CurrentUser
orUpdate-Module -Name AWS.Tools.Installer
). This would greatly improve the customer experience of not just this module but all AWS.Tools.* modules when someone is using the Installer module to maintain their module collection.Use Case
There is no current way for a customer of the AWS.Tools.Installer module to know that their module is out of date when it is being run, despite the fact that this module explicitly checks for all other AWS.Tools.* modules for updates. This makes for a poor customer experience, especially since this module has been greatly improved in recent versions.
Proposed Solution
Implement a check using
Find-Module -Name AWS.Tools.Installer
along with a corresponding override switch parameter (perhaps -NoUpdateCheck) on both
Install-AWSToolsModuleand
Update-AWSToolsModule` commands that will warn if a newer version exists. It would require a slight change to Get-AWSToolsModule as well to remove the filter of the Installer module.Other Information
No response
Acknowledgements
AWS Tools for PowerShell version used
AWS.Tools.Installer 1.0.2.4
PowerShell version used
Operating System and version
Windows 11
The text was updated successfully, but these errors were encountered: