Leave Configuration
Summary
Leave configuration is grouped by responsibility; sensitive names and values are intentionally omitted.
Audience
Developers, architects, DevOps, security, and support engineers.
Overview
| Category | Purpose |
|---|---|
| Database | Persistence provider and service-owned store. |
| Authentication | Token validation metadata and trusted caller identity. |
| Tenant context | Tenant/actor context forwarded to service boundaries. |
| Messaging/outbox | Broker publication, consumer subscription, and retry infrastructure. |
| Attendance dependency | Conflict-check client addressing and timeout behavior. |
| Workflow integration | Optional delegation, workflow identity, and verification behavior. |
| Observability | Service identity, tracing exporters, and structured logging. |
| Migration behavior | Startup schema update ownership. |
| Gateway dependency | Compatibility/direct routing and service discovery. |
Restart/hot-reload behavior is not universally confirmed. Configuration ownership, validation, and production defaults require operational review. Exact keys, values, endpoints, credentials, and non-production bypass settings are excluded.
Source References
microservices/src/leave-service/Program.csmicroservices/src/leave-service/Application/WorkflowIntegration.csmicroservices/src/shared-kernel/Extensions/MessagingExtensions.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
Related Articles
See Also
Keywords
- Leave Service
- Leave Configuration
- Technical architecture
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly