Skip to content

fix: enable notification Kafka listeners - #10

Merged
ramioooz merged 1 commit into
mainfrom
fix/221-enable-kafka-listener
Sep 5, 2026
Merged

ramioooz merged 1 commit into
mainfrom
fix/221-enable-kafka-listener

Conversation

@ramioooz

@ramioooz ramioooz commented Sep 5, 2026

Copy link
Copy Markdown
Member

Summary

  • Explicitly enable Spring Kafka listener processing in Notification Service.
  • Version the deployable image to 0.0.3 and Helm chart to 0.3.0 so Kubernetes recreates the pod with the listener fix.
  • No business API or event contract changes.

Evidence

  • ./mvnw verify: 20 unit tests and 6 integration tests passed.
  • helm lint helm --values helm/values-sit.yaml passed.
  • Helm template renders image digital-bank-java/notification-service:0.0.3.
  • Local SIT validation with the built image:
    • pod Ready 1/1;
    • listener assigned events.transfer.created.v1-0;
    • notification-service consumer group exists;
    • all SIT workloads remained Ready.

Project tracking

Merge guidance

Merge after CI passes. No fixed delay is required because the required topic, configuration, and consumer-factory changes are already merged; after merge, rebuild and roll out image 0.0.3 in SIT, then repeat the listener and consumer-group checks before closing #221.

@ramioooz
ramioooz merged commit d7abe40 into main Sep 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: Notification Service does not start with Kafka consumption enabled

1 participant