This website uses cookies to ensure you get the best experience.
Learn more.
A deployment must keep environment-specific database endpoints separate from application code. Secrets require stronger protection than ordinary configuration. Which approach is suitable?
Published
- Assume every environment must share the same database password forever.
- Treat all resource descriptions as public secret stores.
- Use managed configuration for endpoints and an appropriate protected secret mechanism for credentials, scoped by environment.
- Hard-code production credentials and test endpoints together in the application.
Comments — 0
Sign in to comment