You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to propose adding support for setting the config via environment variables. They would override anything set in the provided json configuration file. Could also make the config path argument optional and the binary would fail to startup if it cannot get a full Config via env vars.
This repo does not have a Discussion section so adding as an issue.
The text was updated successfully, but these errors were encountered:
Support for setting some configuration values as environment variables definitely makes sense.
However, I am not sure if we should support the entire configuration through environment variables.
I understand the use case for few dynamic values or sensitive data, but are there any other advantages to full config through env vars?
One concern, although minor, is that having multiple sources of configuration could make debugging production deployments during operations more confusing.
I wanted to propose adding support for setting the config via environment variables. They would override anything set in the provided json configuration file. Could also make the config path argument optional and the binary would fail to startup if it cannot get a full Config via env vars.
This repo does not have a Discussion section so adding as an issue.
The text was updated successfully, but these errors were encountered: