designate/releasenotes/notes/pluggable-notifications-bd049b755a2ace9c.yaml
Tim Simmons 93c0161242 Make notifications pluggable
- Defines a plugin interface for what's actually emitted as part
  of designate "notifications".
- The default plugin emits the same thing as notifications did prior
  to this patch.
- The "audit" notification plugin emits recordset data changes and
  zone/recordset names, if they exist, the notifications with this
  plugin look like http://paste.openstack.org/show/545210/
- Adds support for multiple notifications for a single change
- Also adds client IP to the context object, as it's a field that
  may be of interest to some types of notifications
- Many tests

Change-Id: I01118fae8ce6e38ccc61b0ce763fd759affd9a86
2017-01-19 16:10:15 +00:00

22 lines
834 B
YAML

---
features:
- Operators now have a choice in the type of notification payload
content that Designate can emit via oslo.messaging's Notifier.
The default plugin is configured to emit the same information
that the notifications previous to this patch emitted. So there
is no functional change.
Operators can write their own notification plugins that exist
in designate/notifications.py.
An "audit" plugin is included. This plugin emits object changes,
if they exist, along with zone ids, zone/recordset names.
A plugin can define multiple payloads from a single notification
to be emitted at once, if desirable.
The selection of a plugin is defined by python entrypoints (for
driver availability) and the new "notification_plugin" option
in the "DEFAULT" config section.