You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STORY: Consume transfer event in notification-service #60
Implementation integration PR opened: digital-bank-java/notification-service#6. PRs #1-#5 were merged into stacked feature branches; PR #6 is required to land the complete notification transfer-consumer stack on main. Related configuration: digital-bank-java/config-repo#33. Preferred merge order: transaction-service integration digital-bank-java/transaction-service#13, then notification-service PR #6, then config-repo PR #33; no delay is required between merges. Keep the consumer disabled until the producer and governed transfer event contract are deployed in SIT.
Verification recorded in the PR: Maven verify, notification consumer/inbox integration coverage, and formatting checks passed. Related configuration remains tracked separately in config-repo PR #33; notification consumption stays opt-in until the producer, event contract, and SIT configuration are deployed.
Activity
ramioooz commentedon Sep 3, 2026
Implementation integration PR opened: digital-bank-java/notification-service#6. PRs #1-#5 were merged into stacked feature branches; PR #6 is required to land the complete notification transfer-consumer stack on
main. Related configuration: digital-bank-java/config-repo#33. Preferred merge order: transaction-service integration digital-bank-java/transaction-service#13, then notification-service PR #6, then config-repo PR #33; no delay is required between merges. Keep the consumer disabled until the producer and governed transfer event contract are deployed in SIT.ramioooz commentedon Sep 4, 2026
Implementation is complete and merged in notification-service PR #6: digital-bank-java/notification-service#6
Verification recorded in the PR: Maven verify, notification consumer/inbox integration coverage, and formatting checks passed. Related configuration remains tracked separately in config-repo PR #33; notification consumption stays opt-in until the producer, event contract, and SIT configuration are deployed.