Fix Version/s: None
Component/s: Stack Documentation and UX
To deploy LTD Keeper in a Docker container (
DM-5194), it’s best practice to handle all configurations through environment variables. In DM-4950, LTD Keeper was configured through files for test and dev/deployment profiles. What we should do is continue to allow hard-coded configurations for test and dev environments, but have a third fully fledged configuration environment that’s driven entirely by environment variables.
The environment variables should allow fine grained configuration (for example, to turn off calls to individual external services for testing).
This should also resolve how to deal with Google Container Engine/Kubernetes auth flow works with environment variables, config files, and profiles.
Thanks for the comments J Matt Peterson [X]!
This is a super simple quick 5-minute review. I just changed how configurations are done towards using configuration classes.