aboutsummaryrefslogtreecommitdiffstats
path: root/functest/utils/env.py
AgeCommit message (Collapse)AuthorFilesLines
2018-02-24Print env vars and env_fileCédric Ollivier1-0/+11
It simply eases detecting wrong inputs [1]. [1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/796/console Change-Id: I0784c29265c69a6ba4a049226196bcdd70b0a572 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-22Switch from CONST to CONFCédric Ollivier1-13/+0
It also removes constants.CONST and env.Environment which are now useless. Depends-On: I764a0a2a24447c941d1e726f3116593b29dd1c1e Depends-On: I6cfa832466dcefd737314633d807512e46267a69 Change-Id: Ife41c59d9f2e6ec4e49df38af962039f99554bc5 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-22Use constants for Functest config fileCédric Ollivier1-2/+2
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>
2018-02-16Get properly env vars or their default valuesCédric Ollivier1-31/+32
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>
2018-02-13Remove INSTALLER_IP from FunctestCédric Ollivier1-1/+0
It's mandatory for testcases which are out of Functest. Change-Id: Ia5f5134334ad9f69d44409d817616fa9033fae95 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Remove obsolote env var IS_CI_RUNCédric Ollivier1-7/+0
Change-Id: I284e0ec97792620db08005a617f584b81a1eae63 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Simplify functest/cli/commands/cli_env.pyCédric Ollivier1-1/+0
CONST shouldn't be used for getting/setting env vars. It adds complexity and may raise side effects. It also removes the obsolete env var CI_DEBUG. Change-Id: I8a8fde0fa781351d5eabd2698ca8aae9dee76fb8 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-01-26Fix last Pylint error in FunctestCédric Ollivier1-30/+32
It also fixes all pylint warnings in router and the related unit tests. tox.ini is updated to ensure that no error is introduced. Change-Id: Iddd74b0dac7b6581d72b04369140006c9e19f998 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-01-16Update set of region identity attributSamuel Bartel1-1/+2
Use OS_REGION_NAME environment variable if defined Change-Id: Ifcdfc468fa4931ab62ac0f3ead103e15af7c0de6 Signed-off-by: Samuel Bartel <samuel.bartel@orange.com>
2017-08-20Allow defining CI_LOOP via envCédric Ollivier1-1/+2
CI_LOOP is more human-readable than BUILD_TAG and could be set by env. Weekly is still the default value even if it can be considered than daily is more relevant. Change-Id: Ia8e370fe0f967ba2c83d0212f8e045d815b4ddb3 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2017-07-05Enable refstack work on https without SSL checksLinda Wang1-1/+2
When refstack is run in https environment, SSL checks will be skipped if no cacert file is provided. JIRA: FUNCTEST-828 Change-Id: Ib44582b4f2f508c7a255a1510dbdc33110fe0f14 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2017-06-19Remove module references __file__Cédric Ollivier1-2/+3
It allows functest to be run directly from a zip file [1]. [1] https://setuptools.readthedocs.io/en/latest/setuptools.html#setting-the-zip-safe-flag Change-Id: I596a71e8cf2bed6dd79655bd5beeb047876a188c Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2017-05-19Set default value for CONFIG_FUNCTEST_YAMLCédric Ollivier1-1/+3
It calculates via the full path of env.py. Change-Id: Ief958833f5116cdb116d0153d85a0ae03063ec5c Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2017-05-17Conform constants.py with the minimal standardsCédric Ollivier1-2/+7
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-20Undo setting CI_DEBUG to true by defaultRomanos Skiadas1-1/+1
Change-Id: I24ca35ada7591e93413cdda1905ee01f77131889 Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
2016-12-22refactor cli module using new constants providerSerenaFeng1-1/+2
JIRA: FUNCTEST-673 Change-Id: I643fb16c694a8d7df45a13237f34b19a02906881 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-12-22Refactor tempest using new constants providerSerenaFeng1-1/+2
JIRA: FUNCTEST-673 Change-Id: Ibc274edd6bc9e8aea9e124fae84d7dec481982ab Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-12-21Refactor test run related modules using new constants providerSerenaFeng1-0/+15
JIRA: FUNCTEST-673 Change-Id: Ia37fb5a08c8fbc4a8acb666565ea887f9ae48b83 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-12-20Add default env variables in ENV classjose.lausuch1-1/+7
Change-Id: Ibca9c7a533796b5a2beae4e13b626f340969a567 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-12-15Unified way to provide configurations and env variables(proposal 1)SerenaFeng1-0/+18
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>