Course contentsShow
← Cloud and Infrastructure
Lesson 1662 of 2,98934. CI/CD FoundationsFree lesson

Manual Approval Gates

Implement manual intervention points where human approval is required before proceeding to critical stages like production.

Manual Approval Gates

What you'll learn: How to pause your CI/CD pipeline at critical junctions to require human verification before proceeding with deployment.

What Are Manual Approval Gates?

A manual approval gate is a deliberate pause point in your automated pipeline where execution stops until a human reviewer explicitly gives permission to continue. Think of it like a drawbridge: traffic (your code) waits until the gatekeeper decides it's safe to lower the bridge and let it cross into the next territory (environment).

While automation is powerful, certain decisions—especially those affecting production systems, customer data, or compliance—benefit from human judgment. Manual gates inject this human oversight into otherwise automated flows.

Where and Why to Use Them

Typical placement points include:

  • Before production deployment: Review metrics, test results, or business readiness
  • After staging validation: Verify that QA sign-off is complete
  • For compliance checkpoints: Ensure regulatory requirements are met
  • High-risk changes: Database migrations or infrastructure modifications

How They Work (Conceptually)

When your pipeline reaches a manual approval gate:

  1. Execution pauses automatically
  2. Notifications alert designated approvers (via email, Slack, etc.)
  3. Approvers review artifacts, logs, or test results
  4. They either approve (pipeline continues) or reject (pipeline stops/rolls back)
  5. The decision is logged for audit purposes

This pattern typically appears after the Conditional Execution Pattern, where logic determines if a gate is needed, and before final deployment stages.

Example Scenario

Your pipeline builds code → runs tests → deploys to staging → [MANUAL GATE] → deploys to production. The gate ensures your team consciously approves each production release rather than letting every passing test automatically reach customers.

Key Takeaway: Manual approval gates balance automation speed with human oversight, providing safety checkpoints at critical pipeline stages without sacrificing the benefits of CI/CD.