Skip to content

stretch(pre-prod): streamline manual deployments and rollbacks process on production

Created by: jhchabran

Context

With the ongoing effort to create a pre-prod and production environment, and to wire it to the CD pipeline, we need to be able to override the system to manually deploy or roll back the cloud production, without disruption from the automated deployments.

This should be a safeguarded mechanism, to avoid inappropriate use or overuse of the mechanism.

Definition of done

  1. As a Sourcegraph teammate without deep familiarity with the infrastructure, I can trigger a production deployment.
  2. As a Sourcegraph teammate without deep familiarity with the infrastructure, I can trigger a rollback to the last known viable deployment.
  3. The two above points are safeguarded by a mechanism guaranteeing restricted access.
    • @jhchabran / @daxmc99 : Define how the mechanism should work. Is it requiring the approval of a specific group of individuals? Should we allow individuals in particular?
  4. If the CD has scheduled a deployment but has not started it yet, the manual deployment must come first.
  5. The manual deployment is announced on Slack, with at least a final update when it completes.

Outcome

  • TBD

Resources