-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
fix ObjectTagging with DeleteMarker #11185
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 48m 21s ⏱️ - 45m 50s Results for commit 9bb688e. ± Comparison against base commit b58b0f8. This pull request removes 1784 tests.
|
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.
Good thinking for the store!
Nice set of extra test to validate the behaviour!
LocalStack doesn't replicate the behaviour of AWS correctly for DeleteMarker with ObjectTagging operations. See localstack/localstack#11180. This issue has been fixed by LocalStack, but has yet to be released in a numbered version. We want to wait until that happens before we enable this test and update our Docker Compose file with a new image version for our LocalStack container. See localstack/localstack#11185.
LocalStack doesn't replicate the behaviour of AWS correctly for DeleteMarker with ObjectTagging operations. See localstack/localstack#11180. This issue has been fixed by LocalStack, but has yet to be released in a numbered version. We want to wait until that happens before we enable this test and update our Docker Compose file with a new image version for our LocalStack container. See localstack/localstack#11185.
LocalStack doesn't replicate the behaviour of AWS correctly for DeleteMarker with ObjectTagging operations. See localstack/localstack#11180. This issue has been fixed by LocalStack, but has yet to be released in a numbered version. We want to wait until that happens before we enable this test and update our Docker Compose file with a new image version for our LocalStack container. See localstack/localstack#11185.
* Update npm dependencies * Ensure Conductor tests run when there are changes in Core * Improve readability of lockS3File Conductor task * Skip E2E test for checking locking of S3 file LocalStack doesn't replicate the behaviour of AWS correctly for DeleteMarker with ObjectTagging operations. See localstack/localstack#11180. This issue has been fixed by LocalStack, but has yet to be released in a numbered version. We want to wait until that happens before we enable this test and update our Docker Compose file with a new image version for our LocalStack container. See localstack/localstack#11185. --------- Co-authored-by: GitHub <noreply@github.com> Co-authored-by: Wen Ting Wang <42817036+chubberlisk@users.noreply.github.com>
Motivation
As reported in #11180, we've had the wrong behavior for DeleteMarker with
ObjectTagging
operations.However, my previous assumptions were wrong due to a mistake in a test, which lead to a design decision in the S3 models (the
S3Bucket
get_object
method signature).We will need to update it to support properly this behavior, however this might break persistence as the previous loaded objects might have the previous signature, and fails when used in the provider. We will need to wait for the next major release to remove the previous parameter
raise_for_delete_marker
and add a new one permitting use to separate behavior between calls fromGetObject
vsGetObjectTagging
(one raiseNoSuchKey
and the otherMethodNotAllowed
).Changes
fixes #11180