A pipeline needs distinct nonsecret configuration values for test and production. Which approach is appropriate?

Published
  1. Environment-scoped variables or parameter inputs with clear ownership
  2. Treat a display label as an automatically injected setting
  3. Store all values only in a developer's unsaved shell history
  4. Hardcode production values in every test task

Comments — 0