Bug #43056
closed
pubsub s3 records pushed to an endpoint don't match documentation
Added by Yuval Lifshitz over 4 years ago.
Updated over 4 years ago.
Description
docs has: https://docs.ceph.com/docs/master/radosgw/notifications/#events
{"Records":[
{
"eventVersion":"2.1"
"eventSource":"aws:s3",
"awsRegion":"",
"eventTime":"",
"eventName":"",
"userIdentity":
}
]}
while actual events are:
{
"eventVersion":"2.1",
"eventSource":"aws:s3",
"awsRegion":"",
"eventTime":"2019-11-27T13:48:54.974829Z",
"eventName":"s3:ObjectCreated:Put",
"userIdentity":
...
}
- Status changed from New to Fix Under Review
- Pull request ID set to 31926
note that the correct format was used when events were pulled from Ceph (both for S3-compliant and non-compliant modes), and problem exists when events are pushed to an endpoint (again, in both modes).
In current endpoint implementations the events are not batched, but in the future they may be batched. In such a case the fix has importance beyond compatibility issues, as it would allow multiple events to be batched in one message (similarly to pull mode).
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #43168: nautilus: pubsub s3 records pushed to an endpoint don't match documentation added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF