Reservation Request - Expired Deletion #202
Description
Background
Reservation Requests that have reached the expired state (completed and archived for 6 months) must be deleted from the operational database (Azure Cosmos DB, MongoDB API) per the system's data retention policy. This ensures compliance with storage limits and keeps the database clean of stale records.
Task Description
- Implement logic to automatically delete Reservation Requests from the operational database once they are marked as expired and the 6-month archival window has elapsed.
- Ensure this process runs on a schedule or is triggered reliably to avoid retention policy violations.
- Log deletion events for observability and auditing (OpenTelemetry/Azure Monitor integration).
- Confirm that all related data (messages, notifications, etc.) are also cleaned up if required by retention rules.
- Update documentation to clarify data retention behavior for Reservation Requests.
Acceptance Criteria
- Reservation Requests in the expired state are deleted after 6 months.
- Deletion is observable via logs and metrics.
- No residual data remains in the database for deleted requests.
- Documentation is updated to reflect retention and deletion logic.
References
- See BRD/SRD: Data Retention Strategy
- ADR: OpenTelemetry, Observability
- Azure Cosmos DB (MongoDB API) deletion requirements
- documents/share-thrift-srd-bronze.md
- documents/share-thrift-brd.md