feat: decouple ingestion pipeline jobs - #223
Merged
Merged
Conversation
plakkara-bc
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Splits the monolithic data ingestion pipeline into three independently runnable jobs. Previously, INGEST_DATA chained into eligibility, which chained into auto-batching and ICM sync-back. Each step now runs as a standalone job with its own entrypoint, so they can be triggered independently from OpenShift or manually.
What Changes
eligible/not_eligible_in_paycontacts and adds them to the pending batch, then syncs back to ICMbackend/src/jobs/entrypoints/auto-batch.ts(runnable asjob:auto-batch)RUN_ELIGIBILITYsuccess timestamp instead ofINGEST_DATAautoBatchContacts()method andautoBatchedfield fromEligibilityService(logic now lives exclusively inAutoBatchService)