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>
This commit is contained in:
parent
9b349ca222
commit
bceb008249
@ -33,7 +33,7 @@ rabbit_notification_exchange = designate
|
||||
rabbit_notification_topic = notifications
|
||||
|
||||
[oslo_messaging_notifications]
|
||||
driver = {% if designate_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
|
||||
driver = {{ (designate_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
|
||||
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 %}
|
||||
|
||||
########################
|
||||
|
Loading…
x
Reference in New Issue
Block a user