Kevin Carter 3439e7826d 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: I9614af2d8a7e908327d2c8ee64f75070dbccfb08 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>		2019-04-24 20:28:44 +00:00
..
blazar.conf.j2	Correct notification driver	2019-04-24 20:28:44 +00:00