A zoning-board API image embeds the production database URL and a plaintext password so “it just works” in prod. What twelve-factor-aligned fix should the team apply before promoting the same artifact to test and production?
Select an answer to reveal the explanation.
Short Explanation
The same sealed jar of preserves should fit every kitchen—only the labels on the shelf change. Externalize config so one artifact runs in test and prod. Baking production URLs into the image forces rebuilds and couples environments.
Full Explanation
Cloud-native configuration lives in the environment: endpoints, credential handles, and flags vary while the built artifact stays constant. Hardcoding production settings inside the image couples environments and requires a rebuild to retarget. Per-environment images, secrets in source, and weakening TLS avoid the real design rule.