Skip to main content

Leave Deployment and Startup

Summary​

Deployments must validate the service artifact, startup/migration outcome, hosted services, gateway reachability, dependencies, and safe smoke evidence.

Audience​

DevOps/SRE, service owners, QA, support, and release approvers.

Overview​

The artifact is built from the Leave Service project/container definition. Startup behavior includes configured persistence initialization and hosted services. A process-health response is necessary but insufficient.

Post-deployment checks should cover direct and compatibility paths appropriate to the environment, projection consumption, relay progress, Attendance conflict behavior, optional Workflow behavior, and correlation-safe logs/traces. Rollback may restore the previous application/routing version, but schema and data compatibility require owner approval; this guide does not prescribe destructive rollback.

Source References​

  • microservices/src/leave-service/Dockerfile
  • microservices/src/leave-service/Program.cs
  • microservices/src/leave-service/Infrastructure/Persistence.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
  • microservices/src/leave-service/Messaging/OutboxRelayHostedService.cs

See Also​

Keywords​

  • Leave operations
  • Leave Deployment and Startup
  • Service support

Revision Information​

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