tree 2a50dbe72a98ca445a019a71be51169555f8651d
parent 7ae41f9036e251ff8e56f4c090842258b07522df
author Pavlo Shchelokovskyy <shchelokovskyy@gmail.com> 1534183158 +0300
committer Ilya Menkov <imenkov@mirantis.com> 1570103385 +0000

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.
Related-prod: PRODX-351
Change-Id: I94a82caf1fcb6999151ff1e6fbbe1e2ba211bbb9
(cherry picked from commit 7a9529a40ccd4a93246a3467d031b3d1fa9bb2cd)
Related-Issue: PROD-21945
(cherry picked from commit 57c65d43be28dc988334639b73ffab91b206a80c)