I’m in favor of all the things in this proposal. I mentioned runtime vs compile time, just because we were talking about config. It’s already an issue today, so it doesn’t have to be solved in this.
This may also be tangentially related, but there are multiple ways to provide configuration besides the ways mentioned here:
- Environment variables (solved for)
- Secrets file in config format e.g. prod.secrets.exs (solved for)
- Individual secrets mounted on the file system. This is common in an environment using docker where a secret is mounted as an in memory disk, which provides better security than an environment variable. (workable, but maybe not ideal)
- A secrets manager, like vault. Where config is leased from a manager that has the ability to invalidate secrets. (not solved for)
This could be moved to another discussion, but I would like the ability to specify another type of configuration provider that may be more suitable for the type of configuration that is being read.
