Compose the Transaction Matcher backend in apps/api and activate the scheduler daemons #48
Labels
No labels
bug
enhancement
pr-split
question
security
transaction-matcher
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
momsse/octant#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from #40 (epic #42).
apps/apicurrently composes only the authentication/authorization backend. The scheduler daemons from #40 (@octant/scheduling:ReconcileDaemonLayer,CreateAccountingPeriodDaemonLayer,SynchroniseBankAccountsDaemonLayer,SynchronizePartyDocumentsDaemonLayer) are defined and tested-by-construction but not yet wired into the running app, because their dependencies (the banking/documents/reconciliation use-cases, queries, repositories, event stores, inline projections) are not composed inapps/api.Work
apps/api:SchedulerConfig.layerand add the four@octant/schedulingdaemon layers toDaemonsLayerinapps/api/src/di/business.layer.ts.This composition is the shared foundation for #41 (API + backoffice), so it likely lands with or just before #41.