Ensure the staging and production are in sync before promoting a package.
Problem
With the introduction of multiple staging environments, staging and production are meant to be kept in sync. During today auto-deploy's:
- A package was promoted
15.4.202209120620-d8c9220c39c.e1f31835888
- A staging deployment failed and was not restarted
- The deployment to production when through.
- When another package was ready to be promoted (
15.4.202209120920-e952d91964c.118a2d203b6
), release managers proceed to promote this package (because none of the production checks failed)
The above events caused staging and production to be out of sync.
Proposal
As part of the production checks executed after the baking time, validate that staging and production environments are running the same package. If they're not, prevent the package promotion and notify release managers about it.
Edited by Mayra Cabrera