-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
implement S3 native bucket versioning #8799
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
35742aa
to
b874cea
Compare
59ee74f
to
6abdab2
Compare
26a399d
to
733f722
Compare
6abdab2
to
08162e0
Compare
9686f44
to
d8dbb04
Compare
08162e0
to
1fd8bd6
Compare
d8dbb04
to
6df3c6d
Compare
1fd8bd6
to
e77d9bf
Compare
e77d9bf
to
61947dd
Compare
@@ -5982,6 +5982,7 @@ def test_post_request_missing_signature( | |||
) | |||
|
|||
# AWS seems to detected what kind of signature is missing from the policy fields | |||
print(response.content) |
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.
will remove in the next PR if possible, as I wouldn't want to rebase everything. It could be merged right after!
61947dd
to
0888220
Compare
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! nice that it's so easy :D i'll let @alexrashed sign off on the serializer change
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.
Awesome! The latest revision of the serializer changes are great and perfectly generalized! 🚀
0888220
to
e86455d
Compare
This PR implements Bucket Versioning in the new native S3 provider. This in turn allowed me to properly tests what I had already written but couldn't test because I couldn't actually enable the versioning, and fix what was wrong.
This PR also contains a new feature in the serializer: we couldn't add headers to exceptions, when S3 actually does that. I'm not sure this is common to all XML protocol based services, so I contained it only in S3 for now. I tried to keep the same existing logic as much as I could, but applied to exceptions.