This website uses cookies to ensure you get the best experience.
Learn more.
A pipeline needs distinct nonsecret configuration values for test and production. Which approach is appropriate?
Published
- Environment-scoped variables or parameter inputs with clear ownership
- Treat a display label as an automatically injected setting
- Store all values only in a developer's unsaved shell history
- Hardcode production values in every test task
Comments — 0
Sign in to comment