[PR #1549/b53f7d72 backport][stable-6] s3_object - fix regression related to leading / in object key names #1554
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #1549 as merged into main (b53f7d7).
SUMMARY
fixes #1548
S3 object key names should not include a leading
/
(https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html). However, for historical reasons we've supported them (we just pruned them out) this pruning was dropped in 6.0.0 without warning.For the sake of simplifying things and moving closer to the actual AWS resources, deprecate pruning out the leading
/
. (Arbitrarily modifying inputs and resource names tends to lead to strange edge cases)ISSUE TYPE
COMPONENT NAME
s3_object
ADDITIONAL INFORMATION
Regression of ansible/ansible#30576 / ansible/ansible#30579