Closed tommymaynard closed 2 years ago
I agree with your point, we will look into this.
We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.
Expected Behavior
Cmdlets that are not specific to an AWS Service should always use the AWS Prefix in their name, after the verb and dash, but before the singular noun, or CamelCase singular nouns.
Current Behavior
Three cmdlets have long been inconsistent with the AWS prefix, prefixed commands. These are:
Possible Solution
I recommend that the above *-DefaultAWSRegion Cmdlets be renamed, and aliases be created that resolve to the three renamed cmdlets. The aliases should use the previous cmdlet names.
Steps to Reproduce (for bugs)
Context
As it stands now, there is a problem with command discovery due to the incorrect placement of this prefix.
Your Environment