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
BUG: add Kafka auto-configuration for MFA assurance publisher #247
After the SIT assurance publisher was enabled by mfa-service#17, the MFA pod fails during startup because KafkaTemplate is not available for MfaAssuranceMessageSender.
Built merged main as digital-bank-java/mfa-service:0.0.6.
Helm release upgraded successfully in digital-bank-sit.
Current deployment is 1/1 Ready.
/actuator/health returned UP.
Kafka assurance publisher configuration is enabled and the in-cluster broker is configured.
No Kafka template startup failure or PostgreSQL outbox timestamp binding error appeared after the successful restart.
The first pod restart was caused by a transient Config Server HTTP 500 during rollout; the replacement pod started successfully and remains healthy. The broader MFA assurance story remains open for end-to-end transfer acceptance.
Activity
ramioooz commentedon Sep 6, 2026
Corrective implementation
Pull request mfa-service#18 contains the corrective implementation.
The merged MFA SIT configuration exposed two runtime defects during rollout:
spring-kafkadependency did not provide Spring Boot Kafka auto-configuration, so the assurance publisher could not createKafkaTemplate;InstantSQL parameters in the assurance outbox poller and update statements.The fix replaces the dependency with
spring-boot-starter-kafkaand binds all outbox timestamps as JDBCTimestampvalues.Verification
./mvnw --batch-mode --no-transfer-progress verify -qpassed.digital-bank-java/mfa-service:0.0.5built successfully.1/1Ready with zero restarts./actuator/healthreturnedUP.Issue remains open until PR #18 is reviewed and merged, then the permanent image release can replace the temporary SIT tag.
ramioooz commentedon Sep 6, 2026
Post-merge SIT closeout
Corrective PR mfa-service#18 is merged.
digital-bank-java/mfa-service:0.0.6.digital-bank-sit.1/1Ready./actuator/healthreturnedUP.The first pod restart was caused by a transient Config Server HTTP 500 during rollout; the replacement pod started successfully and remains healthy. The broader MFA assurance story remains open for end-to-end transfer acceptance.