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: I3ca44a9d70eadeb1a82d5f8aa35ec417de5503d5
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2019-02-07 22:33:37 +00:00
parent d0a23313ea
commit f7bb0d11b1
1 changed files with 1 additions and 1 deletions

View File

@ -56,7 +56,7 @@ policy_dirs = {{ sahara_policy_dirs }}
# Ceilometer options
[oslo_messaging_notifications]
driver = {% if sahara_ceilometer_enabled %}messagingv2{% else %}noop{% endif %}
driver = {{ (sahara_ceilometer_enabled | bool) | ternary('messagingv2', 'noop') }}
transport_url = {{ sahara_oslomsg_notify_transport }}://{% for host in sahara_oslomsg_notify_servers.split(',') %}{{ sahara_oslomsg_notify_userid }}:{{ sahara_oslomsg_notify_password }}@{{ host }}:{{ sahara_oslomsg_notify_port }}{% if not loop.last %},{% else %}/{{ sahara_oslomsg_notify_vhost }}{% if sahara_oslomsg_notify_use_ssl | bool %}?ssl=1{% else %}?ssl=0{% endif %}{% endif %}{% endfor %}
[oslo_messaging_rabbit]