-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
implement S3 native tagging #8811
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
b375bc4
to
c52c498
Compare
59f24eb
to
dd31f9c
Compare
c2e20c6
to
54f3eb4
Compare
dd31f9c
to
659e02d
Compare
38368a7
to
f4da220
Compare
659e02d
to
f0f245f
Compare
4be055c
to
c3e8ef0
Compare
f0f245f
to
6d255bd
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.
the snapshots were generated before the tests directory change. As they're skipped currently when the new provider is not set, it did not come up. This is fixed in a subsequent PR: #8884
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! 🏷️ 🚀
# There a weird AWS validated bug in S3: the returned key contains the bucket name as well | ||
# follow AWS on this one | ||
e.Key = f"{bucket}/{key}" |
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.
s3 intensifies
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 👍🏻
c3e8ef0
to
91d8151
Compare
6d255bd
to
897b718
Compare
This PR implements all tagging related operations and usage:
Tagging with:
TaggingDirective
)As well as S3 notifications support for Put/Delete object tagging.