Skip to content

TASK: Provision transfer-created Kafka topics and enable Notification flow in SIT #200

Closed
digital-bank-java/infra-sit
#29

Description

@ramioooz

Parent: #60
Sprint parent: #23

Objective

Provide the explicit Kafka runtime prerequisites for Notification Service to consume transfer-created events in local SIT.

Scope

  • Provision events.transfer.created.v1 and its dead-letter topic through reviewed SIT infrastructure.
  • Enable the Transaction Service transfer-created publisher using explicit SIT configuration.
  • Keep topic ownership, partition key, retention, retry, and DLQ behavior aligned with the governed event contracts.
  • Verify Notification consumer-group startup and durable inbox processing without relying on Kafka automatic topic creation.

Acceptance Criteria

  • Topics exist before the dependent workloads start and are represented by reviewed infrastructure/configuration changes.
  • Transaction Service emits a governed TransferCreated.v1 event for the supported workflow.
  • Notification Service consumes the event and records the expected durable inbox/work outcome.
  • Duplicate delivery and retry/quarantine behavior remain safe.
  • Related PRs identify merge order and no unnecessary rollout delay.

Related work

This task is runtime enablement only; event schema ownership remains in the governed AsyncAPI contracts.

Activity

  1. added theissue type on Sep 3, 2026
  2. self-assigned this
    on Sep 3, 2026
  3. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Runtime dependency note: the Notification implementation is merged in notification-service#7, but SIT rollout requires the explicit events.transfer.created.v1 topic and publisher enablement tracked by this task.

    The broker has automatic topic creation disabled. Use reviewed infrastructure/configuration changes, then verify the consumer group, durable inbox, duplicate delivery, and quarantine paths. Related configuration is config-repo#33; the governed contract is .github#176.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions