ENV variables not taken if settings subsection defined

[DevNinja90]

Describe the Bug

The defined env vars here Environment Variables

Currently these three ones

SERVER_SECRET | server.secret
EMAIL_SMTP_PASS | email.smtp_pass
POSTGRES_CONNECTION_STRING | postgres.connection_string

Will not be used or taken if any kind of config subsection e.g. server, email or postgres is defined in the settings fine (config.yml)

E.g. i want to define the postgres pool settings in the config.yml but the connection_string inside my secret (k8s deployment). Then the env var is skipped as a section of the subsettings is defined in my config.yml

Verified with the postgres section, but i think this applies to all of them. 😉

Might also apply to gerbil, but not tested.

Environment

• OS Type & Version: (k8s deployment)
• Pangolin Version: 1.13.1

To Reproduce

define some settings in config.yml for postgres and define the connection_string as env var.

Expected Behavior

both configs are respected

[oschwartz10612]

For the postgres string this is because of pangolin/server/db/pg/driver.ts where it looks to only pull it if the postgres section is not defined. I will fix that. For the other two I think they should be overriding correctly but not 100% sure. Could you verify for me if they are actually failing?

[DevNinja90]

Can confirm the others still work. Thanks!