Skip to content

Implement streaming ledger functionality with CRUD operations and job processing - #901

Open
andie23 wants to merge 394 commits into
developmentfrom
sending-api-retry
Open

andie23 wants to merge 394 commits into
developmentfrom
sending-api-retry

Conversation

@andie23

@andie23 andie23 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Context

This change introduces a streaming ledger system to manage and track the status of streaming jobs. The goal is to enhance the reliability and traceability of streaming operations, allowing for better error handling and job retries.

Description

The implementation includes a new StreamingLedger model to store the state of each streaming job, along with CRUD operations for managing these records. The StreamingJob class has been updated to interact with the ledger, marking jobs as queued, sent, acknowledged, or failed based on their processing status. New routes and controller actions have been added to handle ledger queries and acknowledgments.

Changes in the codebase

  • Created a StreamingLedger model with necessary validations and status management.
  • Implemented a StreamingLedgerService to encapsulate business logic related to ledger operations.
  • Updated the StreamingJob to create and manage ledger entries during job execution.
  • Added new routes for streaming ledger operations, including endpoints for querying ledgers and acknowledging streams.
  • Enhanced the StreamingService to include ledger interactions during the streaming process.

Changes outside the codebase

A new database table for streaming_ledgers has been created to store the ledger entries. This includes fields for tracking the status, response codes, and error messages associated with each streaming job.

Additional information

This implementation allows for better monitoring and management of streaming jobs, providing a mechanism to retry failed jobs and track their progress. The design ensures that all relevant information is captured in the ledger for future reference.

Ticket

No specific ticket is referenced for this change.

Screenshots

No visual changes are included in this update.

brian-mw and others added 30 commits September 8, 2025 14:22
…ts-with-arv-not-in-program

Feat/data cleaning patients with arv not in program
…e-amounts

add DC tool dispensed-implausible amounts
pamzey and others added 26 commits June 2, 2026 15:25
Enhance LIMS integration and improve drug management
…b identifiers to prevent duplicate notifications
Pre-Eclampsia was missing the boolean-to-text ternary that other
history fields (Asthma, Diabetes, Epilepsy) already use, causing
raw true/false to print on the visit summary label instead of
YES/NO.
@andie23
andie23 requested a review from Timobify September 10, 2026 11:19
@andie23 andie23 self-assigned this Sep 10, 2026
@andie23
andie23 marked this pull request as draft September 10, 2026 11:20
@Timobify
Timobify marked this pull request as ready for review September 11, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants