- Shipped
- 3 ஆகஸ்ட், 2026 அன்று 4:52 AM UTC
- Author
- Kamo
- Commit
- a1cd493
MfaEnrollmentService is a @Service in kamo-shared-library, so the wildcard @ComponentScan("com.kamo") in this application constructs it whether or not this service has anything to do with MFA — and its constructor needs UserMfaEnrollmentRepository. That package was not in the @EnableJpaRepositories list, so the repository bean did not exist and the context failed to start: Parameter 0 of constructor in **************** required a bean of type ...UserMfaEnrollmentRepository that could not be found Identical shape to the mlos.notification case already documented in SecurityService, which is the only service that had been updated. Every other service with a wildcard component scan and an explicit repository list was going to crash on its next deploy for the same reason. EmailService was already down on this — CrashLoopBackOff, the old replicaset still serving so nothing looked wrong from outside.