This website uses cookies to ensure you get the best experience.
Learn more.
A release secret is rotated. How should the application and pipeline consume its replacement?
Published
- Through the controlled secret reference and rollout process, with validation and removal of obsolete access.
- Commit the new secret to source to ensure every developer receives it.
- Put the secret in the deployment display name.
- Keep the old leaked credential active indefinitely.
Comments — 0
Sign in to comment