We should write a test case that checks whether marshalling from env variables works properly everywhere, so that we notice when someone updates the library and breaks it.
Expected Behavior
To fix this, we need to update our build and test pipelines to include the feature flag -tags=viper_bind_struct
Steps To Reproduce
No response
Relevant logs and/or screenshots, environment information, etc.
Is there an existing issue for this?
Current Behavior
We need to be careful when updating viper beyond v1.18.0
https://github.com/caas-team/sparrow/pull/73#issuecomment-1898997271
We should write a test case that checks whether marshalling from env variables works properly everywhere, so that we notice when someone updates the library and breaks it.
Expected Behavior
To fix this, we need to update our build and test pipelines to include the feature flag
-tags=viper_bind_struct
Steps To Reproduce
No response
Relevant logs and/or screenshots, environment information, etc.
No response
Who can address the issue?
Anyone
Anything else?
No response