How-To Guides
Promote Between Environments
Move validated changes across stages with controlled scope, approvals, and runtime verification.
Task Outcome
Promotion becomes a predictable stage progression activity instead of a high-risk manual jump.
When To Use This Guide
- Moving a proven release from lower to higher environment.
- Managing staged rollout with tenant/service granularity.
- Re-running promotion after a previously blocked attempt.
Prerequisites
- Source environment has stable verification evidence.
- Target environment policy and freeze state are known.
- Required approvers are available.
UI Route Map
- Open
Promotion Pipeline. - Select source and target environments from allowed graph.
- Choose tenant/service scope and run preview.
- Submit promotion request and complete gate checks.
- Execute and verify target runtime state.
Step-By-Step Execution
Select source and target environments according to configured progression chain.
Limit promotion scope to intended tenants/services and run preview.
Confirm target policy requirements and approval expectations.
Submit promotion request and monitor gate progress.
Execute promotion when status is ready and freeze conditions are clear.
Verify runtime health and drift posture in target environment.
Record promotion evidence for future rollback and incident timelines.
Promotion Strategy Options
- Best default for risk control and quick recovery.
- Promote service subsets or tenant subsets first.
- Use only after repeated stable non-production outcomes.
- Needs stronger approval confidence and rollback preparedness.
- Promote limited live traffic scope before broad move.
- Capture runtime evidence between phases.
- Choose rollback mode before execution.
- Ensure on-call ownership is known for target window.
Validation Checklist
- Promotion scope matches intended target subset.
- Approval and freeze requirements are satisfied.
- Target runtime checks are passed after execution.
- Promotion evidence is linked to request and outcome.
Common Failure Modes
- Promoting broad scope without previewing target-specific impact.
- Gate completion assumed from partial approvals.
- Target environment drift ignored before promotion.
- Promotion and unrelated release changes combined in one request.
Promotion Handoff Template
Source environment:
Target environment:
Scope (tenants/services):
Approvals required:
Execution window:
Verification owner:
Fallback owner: