A release secret is rotated. How should the application and pipeline consume its replacement?

Published
  1. Through the controlled secret reference and rollout process, with validation and removal of obsolete access.
  2. Commit the new secret to source to ensure every developer receives it.
  3. Put the secret in the deployment display name.
  4. Keep the old leaked credential active indefinitely.

Comments — 0