Environments and approvals
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
model environments and decide where humans approve.
Planned topics
- Typical path: dev (automatic), staging (automatic, production-like), production (gated).
- Keep staging close to production in shape and configuration; data is synthetic or masked.
- Approvals suit regulated or high-risk changes; routine releases should rely on automated gates.
- Protect production deployment credentials with environment-scoped permissions.
Draft outline details
Demonstration
pipeline config with an environment: production job requiring approval from the owning team.
Check your understanding
What should differ between environments?
Show answer
Configuration and secrets, not the artifact.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.