Prepare 3.6.0 release #1549
Prepare 3.6.0 release #1549
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
ansibullbot
added
community_review
feature
|
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 10m 49s |
softwarefactory-project-zuul
bot
merged commit bb92137
into
ansible-collections:stable-3
…nsible-collections#1549) s3_object - fix regression related to leading / in object key names SUMMARY fixes ansible-collections#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 Bugfix Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION Regression of ansible/ansible#30576 / ansible/ansible#30579 Reviewed-by: Alina Buzachis
ansible-collections#1555) s3_object - deprecate leading slash in object keys SUMMARY Deprecate support for removing leading / from object names AWS APIs don't expect it to be there, pruning it may cause pain in future ISSUE TYPE Feature Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION Deprecation was split from ansible-collections#1549 Reviewed-by: Alina Buzachis
SUMMARY
One last one for the road.
ISSUE TYPE
COMPONENT NAME
changelogs
galaxy.yml
ADDITIONAL INFORMATION