Lift4: Support for Env Vars in configuration
@dpp is already working on this.
Since Oct 19, 2023.
- Dominant language
- Scala
- Stars
- 1.3k
- Forks
- 275
- PR merge metrics
- No merged PRs in 30d
Description
Lift's properties/configuration mechanism is based on named files. However, this means storing secrets (e.g., DB credentials, etc.) in files and potentially checking those files into source control systems. Yikes!!
The industry is moving to using Env Vars for configuration/secrets.
The proposal is to extend Lift's configuration system to support referencing Env Vars from configuration files (Rust has an `env!(...)` macro.
Thus if a line in a configuration file looks like:
`foo.bar.baz=env!("VAR_NAME")`
Lift's configuration system will read the env var and if the env var isn't define, the config system will throw an exception which will halt the Lift boot cycle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.