Follow up on Merging CGS feature to master branches #1945 with non-urgent pending updates #2003
Closed
5 of 28 tasks
Labels
epic
feature-epic
This is to capture a functionality / Topic that encompasses Epics that are limited to a single PI
oss-core
This is an issue - story or epic related to a feature on a Mojaloop core service or related to it
story
Milestone
Goal:
As a
Mojaloop Scheme, based on previous tests and observations from story #1945I want to
fix non-urgent issues in central-settlement while introducing the Continuous Gross Settlement (CGS) model / featureso that
Central-Settlement is aligned with best OSS practices and standardsAcceptance Criteria:
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
STORY to Split out CGS and InterchangeFee CapabilitiesCentral-Settlement: Create settlement rules handler #2056STORY Central-Settlement: Refactor TransferSettlement handler to align with the OSS standards and architectureCentral-Settlement: Refactor handlers model and domain to align with the OSS standards and architecture #2057STORY Move postman CGS tests to TTKMove postman CGS tests to TTK #2061STORY Create a demo video for CGS (using TTK)Create a demo video for Deferred, Continuous Settlement Models using TTK #2062Messaging around usage of Postman, maintenance and TTK as standard validation toolSTORY to realign settlement and admin apisRealign central-settlements and central-ledger/admin APIs #2063STORY change the assertion framework in the narrow integration scripts to be jestrefactor: central-settlement cgs handler unit tests assertion framework to jest #2095STORY for event-sdk implementation in the central-settlementCentral-Settlement v2 CGS support - Integrate Event Framework #1956Done
Pull Requests:
Follow-up:
Dependencies:
Accountability:
The text was updated successfully, but these errors were encountered: