Repository navigation
fix: enable notification Kafka listeners - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.0.3and Helm chart to0.3.0so Kubernetes recreates the pod with the listener fix.Evidence
./mvnw verify: 20 unit tests and 6 integration tests passed.helm lint helm --values helm/values-sit.yamlpassed.digital-bank-java/notification-service:0.0.3.1/1;events.transfer.created.v1-0;notification-serviceconsumer group exists;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.3in SIT, then repeat the listener and consumer-group checks before closing #221.