S3: fix DeleteObjectTagging on current object#13174
Merged
Conversation
1 task
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 1h 39m 22s ⏱️ Results for commit b3a5907. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 19m 57s ⏱️ - 37m 22s Results for commit b3a5907. ± Comparison against base commit 0809063. This pull request removes 2705 tests. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
As reported in #13162, we had an issue when deleting tags on an versioned object without specifying the version id, meaning we'd target the top of the object stack (current object)
This PR addressed it by using the actual retrieved object version id
Changes