ab1725eb6b
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 |
||
---|---|---|
.. | ||
templates | ||
__init__.py | ||
scenario_base.py | ||
test_aodh_alarm.py | ||
test_autoscaling_lb.py | ||
test_autoscaling_lbv2.py | ||
test_base_resources.py | ||
test_octavia_lbaas.py | ||
test_remote_deeply_nested.py | ||
test_server_cfn_init.py | ||
test_server_signal.py | ||
test_server_software_config.py | ||
test_volumes.py |