doc/radosgw: add push_endpoint for rabbitmq

This commit directs users of rabbitmq to use "push_endpoint"
(with an underscore) instead of "push-endpoint" (with a hy-
phen). This commit adds a note that contains such a direct-
ive. It does not alter the examples already present in the
text.

Signed-off-by: Zac Dover <zac.dover@gmail.com>
(cherry picked from commit ddf8295438b14ada04d8bb5dfc23402bedc937b8)

diff --git a/doc/radosgw/notifications.rst b/doc/radosgw/notifications.rst
index dc7520a1b3ce2a52ad5b51cf61d2dbee6da69cb9..b7582550f73bcb6a185c3d0d7511d2eb5307e487 100644 (file)
--- a/doc/radosgw/notifications.rst
+++ b/doc/radosgw/notifications.rst
@@ -96,6 +96,7 @@ Topics
 .. note::
 
     In all topic actions, the parameters are URL encoded, and sent in the message body using ``application/x-www-form-urlencoded`` content type
+   
 
 Create a Topic
 ``````````````
@@ -107,6 +108,8 @@ To update a topic, use the same command used for topic creation, with the topic
 
 .. tip:: Any notification already associated with the topic needs to be re-created for the topic update to take effect
 
+.. note:: For rabbitmq, ``push-endpoint`` (with a hyphen in the middle) must be changed to ``push_endpoint`` (with an underscore in the middle).
+
 ::
 
    POST