-
Notifications
You must be signed in to change notification settings - Fork 398
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
Add abort multipart upload and expire obj del markers to s3 lifecycle #794
Add abort multipart upload and expire obj del markers to s3 lifecycle #794
Conversation
eee8b44
to
5fe4863
Compare
Why does the CICD say
What does that mean? |
It's just waiting for at least two reviewers/approvals. |
It means that the conditions for the "gate" job hasn't been met, so the job hasn't been allowed to run. It's based on the work that the OpenStack folks have done https://dague.net/2013/02/21/the-openstack-gate/ Once triggered (and successful) Zuul will automatically merge the change. Nominally it's a subset of the 'ansible/check' tests and it's used to ensure that between ansible/check having been run and the change being approved another change hasn't been introduced that clashes with this one (for example a function the change depended on being modified in an incompatible manner) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mdavis-xyz Thank you for working on this. Generally this LGTM! Could you also please add a changelog fragment?
check ondemand |
1 similar comment
check ondemand |
Co-authored-by: Alina Buzachis <[email protected]>
Co-authored-by: Alina Buzachis <[email protected]>
Co-authored-by: Alina Buzachis <[email protected]>
Co-authored-by: Alina Buzachis <[email protected]>
I've added the changelog, and changed |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
recheck |
Co-authored-by: Alina Buzachis <[email protected]>
Can someone please open the gate for me? |
Backport to stable-2: 💚 backport PR created✅ Backport PR branch: Backported as #864 🤖 @patchback |
…#794) Add abort multipart upload and expire obj del markers to s3 lifecycle Depends-On: ansible/ansible-zuul-jobs#1247 SUMMARY Fixes #365 #796 ISSUE TYPE Feature Pull Request COMPONENT NAME s3_lifecycle ADDITIONAL INFORMATION I have not run integration tests yet because of #793. I'm unsure about how to name and structure the new arguments. Do I nest them to match the API, or flatten them to match existing arguments? Reviewed-by: Alina Buzachis <None> Reviewed-by: Matthew Davis <None> Reviewed-by: Mark Chappell <None> Reviewed-by: None <None> Reviewed-by: Markus Bergholz <[email protected]> (cherry picked from commit ed3a7a0)
…#794) (#864) [PR #794/ed3a7a0b backport][stable-2] Add abort multipart upload and expire obj del markers to s3 lifecycle This is a backport of PR #794 as merged into main (ed3a7a0). Depends-On: ansible/ansible-zuul-jobs#1247 SUMMARY Fixes #365 #796 ISSUE TYPE Feature Pull Request COMPONENT NAME s3_lifecycle ADDITIONAL INFORMATION I have not run integration tests yet because of #793. I'm unsure about how to name and structure the new arguments. Do I nest them to match the API, or flatten them to match existing arguments?
Updates to the Developer Guidelines SUMMARY Updates for the Developer Guidelines (originally started as ansible/ansible#77598) ISSUE TYPE Docs Pull Request COMPONENT NAME docs/docsite/rst/dev_guidelines.rst ADDITIONAL INFORMATION Validation run can be found at: https://github.com/tremble/amazon.aws/runs/6192239999?check_suite_focus=true Reviewed-by: Felix Fontein <[email protected]> Reviewed-by: Alina Buzachis <None>
Depends-On: ansible/ansible-zuul-jobs#1247
SUMMARY
Fixes
#365#796ISSUE TYPE
COMPONENT NAME
s3_lifecycle
ADDITIONAL INFORMATION
I have not run integration tests yet because of ansible-collections/amazon.aws#924.
I'm unsure about how to name and structure the new arguments.
Do I nest them to match the API, or flatten them to match existing arguments?