This website uses cookies to ensure you get the best experience.
Learn more.
A team must deploy the same infrastructure to test and production while using different resource names and sizes. Which approach best supports repeatability?
Published
- Store every production secret directly in source code
- Parameterized Bicep with separate environment parameter values
- Use resource tags as the deployment language
- Manually duplicate portal clicks without a definition
Comments — 0
Sign in to comment