tree 5031b366b0d43f2a4e40a83b7355fc52d2905be9
parent e4d6583aa6ccb51fab9d9b89d9393843ae2bf199
author Pavlo Shchelokovskyy <shchelokovskyy@gmail.com> 1534183158 +0300
committer ricolin <rico.lin.guanyu@gmail.com> 1570263818 +0800

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