Paths/DevOps Engineer/CI/CD / Release Pipelines
Add an Approval Gate to a Deployment
Production deployments should need a human. Extend a pipeline with a manual trigger and an environment that requires approval before anything ships.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/ci exists○
- File ~/ci/deploy.yml exists○
- The workflow can be started manually○
- The deploy job waits for the build job and targets the production environment○
02Walkthrough
1 of 6 revealed- 01
Create the ci directory
Pipeline files live in the repository; in this lab they live in their own folder.
mkdir ~/ci - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list