chore: Upgrade bff from spring to quarkus - #220
Conversation
|
| @Valid | ||
| VerificationMatchRequest verificationMatchRequest) { | ||
| log.trace("matchInstitutionAndUser start"); | ||
| log.debug(LogUtils.CONFIDENTIAL_MARKER, "matchInstitutionAndUser userDto = {}", verificationMatchRequest); |
|
2 similar comments
|
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
| log.info("Checking IAM permission: onboardingId={}, userId={}, permission={}, productId={}", | ||
| onboardingId, userId, permission, productId); |
| @Override | ||
| public OnboardingData getOnboardingWithUserInfo(String onboardingId) { | ||
| log.trace("getOnboardingWithUserInfo start"); | ||
| log.debug("getOnboardingWithUserInfo id = {}", onboardingId); |





List of Changes
onboarding-bffon Quarkus, aligned with thestructure used by other microservices.
clientpattern infavor of a proper service layer (
OnboardingService/OnboardingServiceImpl) outside theapipackage.grouped sections with comments, renamed
ms_core -> institution).iam,product,auth) and removed remaining unnecessary Spring remnants.config(same approach used iniam/product) and fixed BFF date deserialization issues.Log Injection) through centralized sanitization (OWASP Encode.forJava).integration_tests_onboarding_bff.yml;CucumberSuiteTest(sameconvention as other microservices);
maven-surefire- pluginexclude), soclean installdoes not run it automatically;pull-requests: writewhere notallowed in the reusable workflow chain.
Motivation and Context
This PR originates from the need to experimentally use an AI tool to perform a
migration of
onboarding-bfffrom Spring to Quarkus, while keeping functionalparity and repository standards.
During this migration experiment, a number of issues emerged and were
addressed in this work:
The PR also improves CI reliability by:
mismatch.
Overall goal: validate an AI-assisted migration path from Spring to Quarkus,
with human supervision and targeted corrections, aligned with the technical
and operational standards already adopted across the repository.
How Has This Been Tested?
troubleshooting.
OffsetDateTimedeserialization failures when timezone offset is missing.Screenshots (if appropriate):
N/A
Types of changes
to not work as expected)
Checklist:
AI-assisted development disclosure
This PR was implemented with AI model assistance and supervised by me end-to-
end.
I reviewed all proposed changes and applied targeted manual adjustments where
needed (application logic, security, configuration, and CI workflows) before
finalizing.