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: Ic61c0dc953903a5a531565ae5deb773b348ec2ef Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
parent
2a199a9621
commit
327456e73a
@ -102,5 +102,5 @@ openstack = {{ tacker_etc_dir }}/vim/fernet_keys
|
||||
ssl = {{ tacker_oslomsg_notify_use_ssl | bool }}
|
||||
|
||||
[oslo_messaging_notifications]
|
||||
driver = {% if tacker_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
|
||||
driver = {{ (tacker_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
|
||||
transport_url = {{ tacker_oslomsg_notify_transport }}://{% for host in tacker_oslomsg_notify_servers.split(',') %}{{ tacker_oslomsg_notify_userid }}:{{ tacker_oslomsg_notify_password }}@{{ host }}:{{ tacker_oslomsg_notify_port }}{% if not loop.last %},{% else %}/{{ tacker_oslomsg_notify_vhost }}{% if (tacker_oslomsg_notify_use_ssl | lower) | bool %}?ssl=1{% else %}?ssl=0{% endif %}{% endif %}{% endfor %}
|
||||
|
Loading…
Reference in New Issue
Block a user