Browse Source

Correct notification driver

The notification driver setup was resulting in the driver and connection string
on the same line. This is caused by the case statement and how jinja formats
the template when a case statement is present. This change modifies how the
driver string is created using a ternary, which will eliminate the case
statement and render the value of the diver correctly.

Change-Id: I2645beb3eed1948f66f76fc7eb45e14923abfa78
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Kevin Carter 2 months ago
parent
commit
bceb008249
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      templates/designate.conf.j2

+ 1
- 1
templates/designate.conf.j2 View File

@@ -33,7 +33,7 @@ rabbit_notification_exchange = designate
33 33
 rabbit_notification_topic = notifications
34 34
 
35 35
 [oslo_messaging_notifications]
36
-driver = {% if designate_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
36
+driver = {{ (designate_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
37 37
 transport_url = {{ designate_oslomsg_notify_transport }}://{% for host in designate_oslomsg_notify_servers.split(',') %}{{ designate_oslomsg_notify_userid }}:{{ designate_oslomsg_notify_password }}@{{ host }}:{{ designate_oslomsg_notify_port }}{% if not loop.last %},{% else %}/{{ designate_oslomsg_notify_vhost }}{% if designate_oslomsg_notify_use_ssl | bool %}?ssl=1{% else %}?ssl=0{% endif %}{% endif %}{% endfor %}
38 38
 
39 39
 ########################

Loading…
Cancel
Save