'version' parameter name not consistant for Read-S3Object when comparing to other similar S3 object cmdlets #369
Labels
feature-request
A feature should be added or improved.
module/powershell-cmdlets
p2
This is a standard priority issue
queued
s
Effort estimation: small
Describe the feature
I ran into something that may seem minor, as it affects overall cognitive load when dealing with parameter names when using certain S3 cmdlets.
In this instance, the parameter name for
Read-S3Object
does not follow the same naming scheme as other similar cmdlets for S3 objects.I may have missed some other examples, but it seems pretty clear for some reason
Read-S3Object
has a different parameter name.This always trips me up if I am not thinking about it, as typically I automatically use
-VersionId
as the parameter name when needing to deal with specific versions when using S3 Object cmdlets.Use Case
#1 - Consistency is king
#2 - Not having to remember a different parameter name for a single cmdlet when the rest are the same.
Proposed Solution
To avoid a breaking change, can we have a parameter alias of
-VersionId
added to -VersionOther Information
No response
Acknowledgements
AWS Tools for PowerShell version used
AWS.Tools.S3 4.1.579
PowerShell version used
Operating System and version
Windows 10 and 11
The text was updated successfully, but these errors were encountered: