As the title suggest adding support to read configuration values (values that currently exist in defaults.ini) from ENV variables. This should enable some features (e.g. setting in an YML file env variables so that these can be exposed to the container and read by LocalEGA; flexibility in the way one can work with configuring LocalEGA) for the way we deploy the application.
The way it works it looks first if that environment variable is set otherwise it will look in defaults.ini or in the --conf file provided, thus it does not take away from the current functionality.
Added new logging solution for lega with:
lega:
level: INFO
handlers: [console]
propagate: true
qualname: lega
Fixed also one missing parameter for vault entrypoint gosu lega ega-verify
As the title suggest adding support to read configuration values (values that currently exist in
defaults.ini) from ENV variables. This should enable some features (e.g. setting in an YML file env variables so that these can be exposed to the container and read by LocalEGA; flexibility in the way one can work with configuring LocalEGA) for the way we deploy the application. The way it works it looks first if that environment variable is set otherwise it will look indefaults.inior in the--conffile provided, thus it does not take away from the current functionality.Added new logging solution for lega with:
Fixed also one missing parameter for vault entrypoint
gosu lega ega-verifyA list of environment variables as well as other specific configuration settings has been compiled here: https://github.com/NBISweden/LocalEGA/wiki/Configuration-Settings-%7C-Environment-Variables