Config Outside the Build

Config is the boundary between a reusable artifact and an environment. The config test Ask whether the value changes per deploy. Credentials, endpoints, queue names, region IDs, and operational switches usually do. Those should be supplied by the environment, not committed into the app. The build-time exception Some settings genuinely shape the artifact: target architecture, compiled asset path, or a static public build ID. Those are build inputs, not runtime secrets. The trap Teams often hide config in image layers because it feels convenient. That convenience fails during incident response, secret rotation, and environment promotion.

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in