[Common] Prevent a secret that is used in prod and dev only from being rotated in a file

Problem to solve

In most cases it is the same secret for prod and dev and sometimes the same secret is only changed in a file, causing disruption to the service when it is a critical secret.

Intended users

Proposal

validate that the change is made in both files when the same secret exists and add a check in the CI that verifies it

Steps

• Make sure that the code contributions checklist has been followed.

What does success look like, and how can we measure that?

Links / references