Fix config test: ignore all env vars in test environment #10835
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change in #10803 to remove the
env -i
flag todocker-compose run
in favor of moving these variables into thedev/environment
file instead had the effect of inserting all environment variables indev/environment
into the test environment when run viamake tests
This didn't affect any tests except for
test_config
, which was making assumptions about what environment variables were present in the test environment. To remedy this, we make the test explicitly ignore all environment variables in the test environment to restore it's intended behavior.Also cleans up the test a bit.