Leave Cutover and Rollback

Summary

Leave ownership transition is gateway-controlled and requires parity, dependency, reconciliation, and rollback evidence; no dedicated Leave cutover runbook was found.

Audience

Release approvers, gateway/Leave owners, DevOps/SRE, QA, architects, and product owners.

Overview

Exact routing-toggle names and private topology are excluded. Validate direct and compatibility contracts, safe smoke results, data coherence, dependency readiness, and consumer effects before approval.

Current gaps include no Leave-specific cutover/go-no-go asset found, incomplete automated reconciliation, process-only health, and unresolved authorization/policy parity. Rollback must respect schema/data compatibility and approved change management; never use direct data edits.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/scripts/smoke-leave.ps1
• microservices/src/leave-service/Api/LeaveEndpoints.cs
• Controllers/LeaveRequestsController.cs

Related Articles

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Cutover and Rollback
• Service support

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly