Hi Artem, Thanks for noting that. Submitted a doc fix here: https://github.com/ceph/ceph/pull/54136 Yuval On Sat, Oct 21, 2023 at 3:04 AM Zac Dover <zac.dover@xxxxxxxxx> wrote: > Artem, > > Thanks for this, but I don't quite understand what should be changed. Your > suggested change is present in the documentation as of > e25a7e86e9ca5acc11171d536e386277a783760d. > > Zac Dover > Upstream Docs > Ceph Foundation > > > > ------- Original Message ------- > On Saturday, October 21st, 2023 at 1:13 AM, Artem Torubarov < > torubarov.a.a@xxxxxxxxx> wrote: > > > > > > > > Hi, > > > > > > The latest documentation > > > https://docs.ceph.com/en/latest/radosgw/s3-notification-compatibility/#supported-destination > > > > says that: > > > > "pulling and acking of events stored in Ceph (as an internal > destination)." > > is a valid source for s3 notifications. > > > > If i got it right, pull-based subscription was possible only with radosgw > > PubSub sync module, which was removed in reef release > > https://docs.ceph.com/en/latest/releases/reef/#:~:text=The pubsub > functionality for storing,notifications%2C and acking the notifications > > > > . > > > > Suggested changes: > > Currently, we support: HTTP/S, Kafka and AMQP. And also support pulling > > and acking of events stored in Ceph (as an internal destination). > > > > > > Best regards, > > Artem > > _______________________________________________ > > ceph-users mailing list -- ceph-users@xxxxxxx > > To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |