Use `viper` to handle ENV variables in config #1398

New issue

Open

opened 2025-12-28 17:22:51 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:22:51 +00:00

Owner

Originally created by @End-rey on GitHub (Apr 11, 2025).

I'm always frustrated when we write our own ENV variable handler when it can be solved using the library viper.

Describe the solution you'd like

Update the viper library to the version when there is a built-in handler for ENV variables in the function UnmarshalExact and do not use your own handler.

Describe alternatives you've considered

Keep it as is, it works.

Additional context

The main feature has already been implemented https://github.com/spf13/viper/pull/1429, but now it is experimental and has some problems, for example https://github.com/spf13/viper/issues/1732.
Own handler has appeared in #3247 and #3288.

Originally created by @End-rey on GitHub (Apr 11, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when we write our own ENV variable handler when it can be solved using the library `viper`. ## Describe the solution you'd like Update the `viper` library to the version when there is a built-in handler for ENV variables in the function `UnmarshalExact` and do not use your own handler. ## Describe alternatives you've considered Keep it as is, it works. ## Additional context The main feature has already been implemented https://github.com/spf13/viper/pull/1429, but now it is experimental and has some problems, for example https://github.com/spf13/viper/issues/1732. Own handler has appeared in #3247 and #3288.