6c8b05f3cf
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 |
||
|---|---|---|
| config_tempest | ||
| doc | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
python-tempestconf
Overview
python-tempestconf will automatically generate the tempest configuration based on your cloud.
- Free software: Apache license
- Documentation: https://docs.openstack.org/python-tempestconf/latest/
- Source: https://git.openstack.org/openstack/python-tempestconf
- Bugs: https://storyboard.openstack.org/#!/project/912
- Release notes: https://docs.openstack.org/releasenotes/python-tempestconf