Fix AbortMPU conditional deletion of wrong data#5849
Conversation
Hello williamlardier,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files
@@ Coverage Diff @@
## development/8.8 #5849 +/- ##
================================================
Coverage 65.08% 65.08%
================================================
Files 188 188
Lines 11948 11948
================================================
Hits 7776 7776
Misses 4172 4172
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Add functional tests to cover scenarios where aborting an MPU could delete data from a different, completed MPU with the same object key. This prevents a regression of a bug where the wrong data was deleted because the uploadId was not being checked when looking for object metadata to clean up during an abort. Issue: CLDSRV-668
Issue: CLDSRV-668
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-668. Goodbye williamlardier. The following options are set: approve, create_integration_branches |
Issue and context in: CLDSRV-668