Leave Configuration Reference
Summary
Configuration is documented by category only; exact keys and values are intentionally excluded.
Audience
DevOps/SRE, service owners, support engineers, security reviewers, and architects.
Reference Content
| Category | Purpose | Required or optional | Safe operational effect | Owner | Restart requirement |
|---|---|---|---|---|---|
| Database | Persist tenant-scoped Leave data | Required for normal operation | Enables transactional Leave storage when available and compatible | Database and Leave owners | Requires confirmation |
| Authentication | Validate service callers | Required | Rejects callers that cannot establish approved identity | Identity/security and Leave owners | Requires confirmation |
| Tenant context | Resolve tenant boundary | Required per business request | Scopes supported operations to the resolved tenant | Platform/Identity and Leave owners | Not applicable to request data |
| Messaging | Publish/consume integration events | Required for confirmed asynchronous integrations | Enables eventual projection and downstream delivery | Messaging and service owners | Requires confirmation |
| Outbox | Control relay polling/retry behavior | Required for confirmed outbound delivery | Governs background publication progress | Leave owner | Requires confirmation |
| Employee projection | Consume Employee events | Required for synchronized local profiles | Keeps Leave-local employee context current | Employee integration and Leave owners | Requires confirmation |
| Attendance dependency | Check conflicts | Used on confirmed request/decision paths | Prevents supported Leave/Attendance overlap | Attendance and Leave owners | Requires confirmation |
| Workflow dependency | Enable delegated decisions | Optional where confirmed | Selects direct versus Workflow-managed decisions | Workflow and Leave owners | Requires confirmation |
| Observability | Emit structured logs/traces | Operationally required; exporter optional | Provides correlation and diagnostic evidence | DevOps/SRE | Requires confirmation |
| Migration behavior | Apply/verify schema evolution | Environment-controlled | Aligns the running artifact with its expected schema | Database and Leave owners | Startup-related |
| Service identity | Identify authenticated service calls | Required for protected integrations | Establishes service caller identity | Identity/security | Requires confirmation |
| Gateway routing | Select ownership/compatibility path | Transitional | Directs supported traffic to the approved owner | Gateway owner | Requires confirmation |
Do not copy secret-bearing configuration into tickets or documentation.
Source References
microservices/src/leave-service/Program.csmicroservices/src/leave-service/appsettings.jsonmicroservices/src/leave-service/Application/Common/Abstractions.cs
Related Articles
See Also
Keywords
- Leave operations
- Leave Configuration Reference
- Service support
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly