doc/rgw/notifications: specify which event types are enabled by default

Fixes: https://tracker.ceph.com/issues/63530
Signed-off-by: Yuval Lifshitz <ylifshit@redhat.com>
(cherry picked from commit 4ea87307e7af088dc056c1c7785aef7ca9be78b1)

diff --git a/doc/radosgw/notifications.rst b/doc/radosgw/notifications.rst
index 1d18772b29640046eb2f1bc0dd4bfd08d1249649..6c48483269e5c71534718a5235c1ba61f41012b9 100644 (file)
--- a/doc/radosgw/notifications.rst
+++ b/doc/radosgw/notifications.rst
@@ -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

diff --git a/doc/radosgw/s3/bucketops.rst b/doc/radosgw/s3/bucketops.rst
index 17da3a9351d9ab05ac8d4d8ca162f660ad29f717..984733fff7503c929e8ff0ae6f51b78447346dca 100644 (file)
--- a/doc/radosgw/s3/bucketops.rst
+++ b/doc/radosgw/s3/bucketops.rst
@@ -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       |
 +-------------------------------+-----------+--------------------------------------------------------------------------------------+----------+