Pavlo Shchelokovskyy ab1725eb6b 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		2019-10-05 16:23:38 +08:00
..
common	Skip tests based on service features disabled in tempest	2019-01-24 18:53:28 +05:30
services	Merge "Use configured endpoint instead of hardcoded ones"	2018-07-19 10:18:30 +00:00
tests	Allow to pass --insecure options into VMs	2019-10-05 16:23:38 +08:00
__init__.py	Initial movement to new repo with cleanup	2017-11-14 20:28:32 +05:30
config.py	Allow to pass --insecure options into VMs	2019-10-05 16:23:38 +08:00
plugin.py	Add function descriptions for tempest plugin	2018-08-09 08:43:57 +00:00