Read-S3Object fails in V5 for keys with a leading slash #389
Description
Describe the bug
The following command works as expected - retrieves the file from S3 - with V4 (tested with AWS.Tools.S3 v4.1.855);
Read-S3Object -BucketName my-bucket -Key /path/test.txt -File C:/test/test.txt
However when we updated to V5 (test with AWS.Tools.S3 v5.0.9), the same command returns an exception: 'The specified key does not exist'.
Out of curiosity, I checked the same command with the leading slash removed, which works;
Read-S3Object -BucketName my-bucket -Key path/test.txt -File C:/test/test.txt
Is this expected behaviour, or will this be fixed in a future release of V5?
Regression Issue
- Select this option if this issue appears to be a regression.
Expected Behavior
Should retrieve the file from S3
Current Behavior
Exception: 'The specified key does not exist'.
Reproduction Steps
Read-S3Object -BucketName my-bucket -Key /path/test.txt -File C:/test/test.txt
Possible Solution
No response
Additional Information/Context
No response
AWS Tools for PowerShell version used
AWS.Tools.S3 v5.0.9
PowerShell version used
Name Value
PSVersion 5.1.20348.2849
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.20348.2849
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Operating System and version
Windows Server 2022