|
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>
|
SerenaFeng
jose.lausuch