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: If361de5d4112a9e7235972dc7bc5e857c68fef06 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
parent
efd079420c
commit
2edb1b1a4d
@ -71,7 +71,7 @@ rabbit_notification_exchange = glance
|
||||
rabbit_notification_topic = notifications
|
||||
|
||||
[oslo_messaging_notifications]
|
||||
driver = {% if glance_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
|
||||
driver = {{ (glance_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
|
||||
transport_url = {{ glance_oslomsg_notify_transport }}://{% for host in glance_oslomsg_notify_servers.split(',') %}{{ glance_oslomsg_notify_userid }}:{{ glance_oslomsg_notify_password }}@{{ host }}:{{ glance_oslomsg_notify_port }}{% if not loop.last %},{% else %}/{{ glance_oslomsg_notify_vhost }}{% if glance_oslomsg_notify_use_ssl | bool %}?ssl=1{% else %}?ssl=0{% endif %}{% endif %}{% endfor %}
|
||||
|
||||
[paste_deploy]
|
||||
|
Loading…
Reference in New Issue
Block a user