openstack/keystone
Code Issues Proposed changes

Document priority level on Keystone notifications

Browse Source 
In the notification docs, we never explicitly say that notification are
always set at the INFO level. This priority level is not configurable
by the end user through the keystone.conf and this change documents that
behavior in the event_notifications.rst docs.

Change-Id: I293db2b69a73a1b56fe0539e183ea13b87ce639a
This commit is contained in:
Lance Bragstad 2014-02-04 20:55:46 +00:00
parent b30b06e008
commit a146bae224
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/event_notifications.rst
View File

@ -57,6 +57,10 @@ Notifications for create, update and delete events are all similar to each
other, where either ``created``, ``updated`` or ``deleted`` is inserted as the
``<operation>`` in the above notification's ``event_type``.
The ``priority`` of the notification being sent is not configurable through
the Keystone configuration file. This value is defaulted to INFO for all
notifications sent in Keystone's case.
If the operation fails, the notification won't be sent, and no special error
notification will be sent. Information about the error is handled through
normal exception paths.