From a146bae2247560d50cc21462f22f215c0acb1cd7 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Tue, 4 Feb 2014 20:55:46 +0000 Subject: [PATCH] Document priority level on Keystone notifications 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 --- doc/source/event_notifications.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/event_notifications.rst b/doc/source/event_notifications.rst index 5e21105113..44e6b6d41a 100644 --- a/doc/source/event_notifications.rst +++ b/doc/source/event_notifications.rst @@ -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 ```` 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.