I've stumbled upon a bug reported here:
#6473
If configure my codeception.yml like this
params:
- .env # load params from .env file
- env # load params from environment varsand a value comes both from .env file and ENV variable then the .env value is always used (no matter in which order you load the params).
In the original ticket the issue was fixed in #6477 however only SymfonyDotenv section was changed, could it be that the bug is still in if using PhpDotenv?
|
if ( |
|
class_exists(PhpDotenv::class) && |
|
class_exists(RepositoryBuilder::class) && |
|
method_exists(RepositoryBuilder::class, 'createWithDefaultAdapters') |
|
) { |
|
$repository = RepositoryBuilder::createWithDefaultAdapters()->make(); |
|
$dotenv = PhpDotenv::create($repository, codecept_root_dir(), codecept_relative_path($file)); |
|
return $dotenv->load(); |
|
} |
Using verions 5.2.2 at the moment:
> php vendor/bin/codecept --version
Codeception 5.2.2
I've stumbled upon a bug reported here:
#6473
If configure my
codeception.ymllike thisand a value comes both from .env file and ENV variable then the .env value is always used (no matter in which order you load the
params).In the original ticket the issue was fixed in #6477 however only
SymfonyDotenvsection was changed, could it be that the bug is still in if usingPhpDotenv?Codeception/src/Codeception/Lib/ParamsLoader.php
Lines 129 to 137 in cb4c200
Using verions 5.2.2 at the moment: