aboutsummaryrefslogtreecommitdiffstats
path: root/functest/utils/constants.py
AgeCommit message (Collapse)AuthorFilesLines
2017-05-17Conform constants.py with the minimal standardsCédric Ollivier1-11/+8
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>
2017-02-02Change permissions of python filesCédric Ollivier1-0/+0
Change-Id: I21826594ffa9b06a70664aa3512f0b5df8b546cd Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-12-15Unified way to provide configurations and env variables(proposal 1)SerenaFeng1-0/+20
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>