The Externalized Configuration Pattern in a Docker Environment

The application should just be built once by the first stage of the deployment pipe line, and then you can run it in multiple environments. The configuration properties of external services, like the ta base, however, can't be hard wired into the sauce code because they're different in each environment. And so you need an externalized configuration mechanism for doing that. In a docker environment, where it's easy, whether you like teves and cubenetes, why you have a config map That defines some of some property values that then get injected into container as environment varobles.