Fix tests for recent change to environment variables
Recently we switched to a configuration with consistent use of environment variables: https://git.gfz-potsdam.de/dynamicexposure/rabotnik/rabotnik/-/merge_requests/75
Unfortunately the way this is implemented, and suggested by @marius , breaks the tests on the instances (like rabotnik-obm
) that rely on rabotnik
. While this is nothing crucial, we need the tests back to have the CI pipeline turning green. I am wondering what would be the best approach to it and would like to know @marius opinion.
One easy and maybe dirty way around this, would be to set the environment variables in the tests of the instances, although they are not being used, just to avoid the error. Or we think about a clean way in rabotnik
to deal with this situation. What do you think, @marius?