-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare 4.3.0 release #1548
Prepare 4.3.0 release #1548
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 13s |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 11m 14s |
a0ce161
into
ansible-collections:stable-4
…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
SUMMARY
Prepare 4.3.0 release
ISSUE TYPE
COMPONENT NAME
changelogs
galaxy.yml
ADDITIONAL INFORMATION