Age | Commit message (Collapse) | Author | Files | Lines |
|
env_file can't be defined in a config file simply because it's an
entry point (Jenkins jobs, end users)
Change-Id: Ie23c0ef90efc839d60f0f3a9754c58746b1f3a00
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It defines env.get() as an unique way to get Functest env vars or
their default values. It can be considered as a wrapper above os.environ.
It enforces backward compatibility via CONST which mustn't be used
for that purpose. It should be noted that it also stops using CONST
for getting OpenStack env vars.
Change-Id: I333dc1afbc0123166a7eaff8b551370098efa341
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Use setattr instead of internal method (__setattr__).
It must be completed by patches fixing [1] [2] and [3].
[1] https://jira.opnfv.org/browse/FUNCTEST-930
[2] https://jira.opnfv.org/browse/FUNCTEST-931
[3] https://jira.opnfv.org/browse/FUNCTEST-932
Change-Id: I9558f33f5ed4559b6031d75951d5637c0c0ef8cb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
All utils which are moving to xtesting are now fixed.
It remains OpenStack and Functest utils (+ the related unit tests)
which doesn't move to the new package.
Change-Id: If13c627c8444c62d5c6bf9c8057d6413aa0e56c7
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It adds the shebang to constants.py and its dependencies and stops
importing from a relative path. It stops printing obsolete values too.
It adds python3 support to them by the way.
Change-Id: Ie7bddcf253eb245844d9e11c17acc69943c1ba63
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I21826594ffa9b06a70664aa3512f0b5df8b546cd
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
In this proposal, everything in os.environ can be accessed directly using const,
and with the exact name os.environ defined.
The name of a configuration is totally decided by config_functest.yaml,
which is the joint name of each level with '_'.
This version requires us to naming each level in yaml in a little cleancode way,
or else the configuration name would become ugly. Let me take the current
defination of general.directories as instance, the configuration name will be
'directories_dir_repo_functest', looks not very good. But if we make some adaption:
general:
dir:
repo_functest:
it will become 'dir_repo_functest', looks a little better.
For vIMs is well defined, let me take it for example, the configuration names will look like:
vIMS_clearwater_blueprint_url
vIMS_clearwater_blueprint_file_name
vIMS_clearwater_blueprint_name
vIMS_clearwater_blueprint_branch
vIMS_clearwater_blueprint_destination_folder
vIMS_clearwater_deployment-name
Change-Id: I18ec8686d9cfb2b80a370d422c6ad81a8800585c
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|