after a discussion in the RGW standup meeting, we decided that deletion of delete markers will trigger notifications.
however, to distinguish them from other deletions, there will be a new event type for these notifications:
ObjectRemoved:DeleteMarkerDeleted
since they don't represent deletion of an object, these notifications will not include information like: size, and etag
regarding multipart upload, we would not send the "Post" and the "Put" notifications to prevent confusion with other "Post" and the "Put" notifications.
On Sun, Jun 20, 2021 at 4:24 PM Yuval Lifshitz <ylifshit@xxxxxxxxxx> wrote:
Dear Community,Currently, there are several events that could be sent as bucket notifications but are missing some critical information from their objects:* "Post" event sent at the beginning of a multipart upload - when multipart start there is no information on the size of the object, its etag, and other content related attributes* "Put" event for a part during a multipart upload - there is only information o the specific part being uploaded, which is usually less useful for the recipient of the notification. In addition, this could be confusing, since the final object does not exist yet* "Delete" event when a deletion marker is being deleted. Unlike the case of creation of a deletion marker (where there is information on the version that was deleted) in the case of deletion of a deletion marker no information on the deleted object existsSo, the plan is not to send notification in the above cases, however, since this would be a behavior change to the RGW, I would like to make sure that this won't break existing integrations.Your feedback is welcome!Yuval
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
