Release v1.1.0-final introduced a bug which led to the OVERRIDE_DEFAULTS flag not being parsed correctly.
This was caused by the check on the flag being moved to its own script and multiple loads of the .env file with source .env, once within the script and once outside it.
Expected behavior
The following environment variables manually configured in .env should take precedence over the values supplied by the specific branch or image.
Describe the bug
Release v1.1.0-final introduced a bug which led to the
OVERRIDE_DEFAULTS
flag not being parsed correctly.This was caused by the check on the flag being moved to its own script and multiple loads of the
.env
file withsource .env
, once within the script and once outside it.https://github.com/PowerLoom/snapshotter-lite-v2/blob/ffa7496056041e627533027a152c90bc6f9cd0f2/_override_defaults.sh#L1-L11
To Reproduce
Affected versions:
Steps to reproduce the behavior:
OVERRIDE_DEAFULTS=true
in.env
./build.sh
or./build-dev.sh
Expected behavior The following environment variables manually configured in
.env
should take precedence over the values supplied by the specific branch or image.Proposed Solution Place the code block within
build.sh
orbuild-dev.sh
instead of its own script file.Caveats NA
Additional context NA