python-tempestconf/config_tempest
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
..
services Remove static class loader 2018-08-27 17:17:41 +02:00
tests Set use_dynamic_credentials with a priority 2018-10-31 10:26:38 +00:00
__init__.py Refactored python-tempestconf to work with devstack 2017-01-18 17:47:00 +05:30
accounts.py Don't expose credentials 2018-08-10 14:38:15 +00:00
clients.py Replace tenant by project, part 2 2018-06-22 10:42:06 +00:00
constants.py Removing dependence of SERVICE_EXTENSION_KEY 2018-08-08 15:09:51 +02:00
credentials.py Create utils.py 2018-08-13 11:57:14 +02:00
flavors.py Fix: return the flavor ID on autodetection 2018-08-06 20:32:34 +02:00
main.py Set use_dynamic_credentials with a priority 2018-10-31 10:26:38 +00:00
tempest_conf.py More compatibility with Python 3 2018-06-26 23:20:52 +02:00
users.py Merge "Replace tenant by project, part 2" 2018-06-27 12:44:52 +00:00
utils.py Create utils.py 2018-08-13 11:57:14 +02:00