Martin Kopec 6c8b05f3cf Set use_dynamic_credentials with a priority
When an accounts.yaml file is used, python-tempestconf
has to set use_dynamic_credentials to False, otherwise
the generated tempest.conf doesn't work with Tempest.
However, values from a deployer input file are set with
a priority, so that they are not overriden during
discovery.

To fix the issue, use_dynamic_credentials has to be set
with priority too.

The related unit tests checks only a return value from
set function. The patch improves them, so that they
check if a value was overriden when it was supposed to
and the other way around.

Story: 2004140
Task: 27606
Depends-On: https://review.openstack.org/#/c/614312/
Change-Id: I76b8cf694116801e36587929bf320e5743534791
2018-10-31 10:26:38 +00:00
2018-08-08 13:10:19 +00:00
2018-08-10 14:38:15 +00:00
2018-08-17 01:35:00 +00:00
2016-08-24 17:21:57 +02:00
2018-07-18 08:03:26 +00:00
2016-08-24 17:21:57 +02:00
2018-09-07 15:07:53 +02:00
2018-06-05 15:13:26 +00:00
2016-08-24 17:21:57 +02:00
2018-07-16 14:50:11 +00:00
2018-07-02 09:21:17 +00:00
2018-06-26 23:20:52 +02:00

python-tempestconf

Overview

python-tempestconf will automatically generate the tempest configuration based on your cloud.

Description
Automatic Tempest Configuration Generator
Readme 8.2 MiB
Languages
Python 99.8%
Jinja 0.2%