tree e7d1f7e71809625b92715dc9197ca02f9de0b13f
parent 276f3d0e3275b064e6127d3c84f2923c73984c74
author Pavlo Shchelokovskyy <shchelokovskyy@gmail.com> 1534183158 +0300
committer Maksym Shalamov <mshalamov@mirantis.com> 1543410560 +0200

Allow to pass --insecure options into VMs

currently Heat tests have troubles running when self-signed SSL CA is
used on public Heat API and standard upstream images (Cirros, Ubuntu)
are used as those lack trust to those CA - example is DevStack
with tls-proxy service enabled.

A workaround is to set [clients_heat]insecure=True, but that is
not really a production-ready setting, and does not work for CFN-style
signaling, only for WaitConditions.

Instead, this patch adds an extra config option
`vm_to_heat_api_insecure` (defaults to False), and when enabled tests will
pass the correct option to the curl or cfn-signal commands running from
instance's user data via new parameters that test templates are now
accepting.

Change-Id: I94a82caf1fcb6999151ff1e6fbbe1e2ba211bbb9
(cherry picked from commit 7a9529a40ccd4a93246a3467d031b3d1fa9bb2cd)
Related-Issue: PROD-21945