]> git.apps.os.sepia.ceph.com Git - ceph.git/commitdiff
doc/rgw/notifications: specify which event types are enabled by default 54499/head
authorYuval Lifshitz <ylifshit@redhat.com>
Tue, 14 Nov 2023 15:28:45 +0000 (15:28 +0000)
committerYuval Lifshitz <ylifshit@redhat.com>
Tue, 14 Nov 2023 15:30:07 +0000 (15:30 +0000)
Fixes: https://tracker.ceph.com/issues/63530
Signed-off-by: Yuval Lifshitz <ylifshit@redhat.com>
doc/radosgw/notifications.rst
doc/radosgw/s3/bucketops.rst

index a38ad9e01bdfb323110815617f054a6c851b8057..314e0ba6f1677b61b851f7ba5428a6d2858cb849 100644 (file)
@@ -16,7 +16,7 @@ with buckets it owns.
 
 A notification entity must be created in order to send event notifications for
 a specific bucket. A notification entity can be created either for a subset
-of event types or for all event types (which is the default). The
+of event types or for all "Removed" and "Created" event types (which is the default). The
 notification may also filter out events based on matches of the prefixes and
 suffixes of (1) the keys, (2) the metadata attributes attached to the object,
 or (3) the object tags. Regular-expression matching can also be used on these
index 17da3a9351d9ab05ac8d4d8ca162f660ad29f717..984733fff7503c929e8ff0ae6f51b78447346dca 100644 (file)
@@ -537,7 +537,8 @@ Parameters are XML encoded in the body of the request, in the following format:
 | ``Topic``                     | String    | Topic ARN. Topic must be created beforehand                                          | Yes      |
 +-------------------------------+-----------+--------------------------------------------------------------------------------------+----------+
 | ``Event``                     | String    | List of supported events see: `S3 Notification Compatibility`_.  Multiple ``Event``  | No       |
-|                               |           | entities can be used. If omitted, all events are handled                             |          |
+|                               |           | entities can be used. If omitted, all "Created" and "Removed" events are handled.    |          |
+|                               |           | "Lifecycle" and "Synced" event types must be specified explicitly.                   |          |
 +-------------------------------+-----------+--------------------------------------------------------------------------------------+----------+
 | ``Filter``                    | Container | Holding ``S3Key``, ``S3Metadata`` and ``S3Tags`` entities                            | No       |
 +-------------------------------+-----------+--------------------------------------------------------------------------------------+----------+