[#1998] Upgrade to Quarkus 3.8 and switch to @ConfigMapping
#1999
Conversation
This file contains 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
At some point in the future, we will retire the legacy config classes so let's migrate to the new @ConfigMapping infrastructure. I was conservative and only updated to Quarkus 3.8. Note that there might be more optimizations possible with having all elements in a single map but I tried to be as less intrusive as possible as I don't know the codebase.
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.
Description
Update Quarkus to 3.8 as the minimum version and switch to the new
@ConfigMappinginfrastructure.Related Issue
#1998
Motivation and Context
At some point in the future, we will retire the legacy config classes so let's migrate to the new @ConfigMapping infrastructure.
I was conservative and only updated to Quarkus 3.8.
Note that there might be more optimizations possible with having all elements in a single map but I tried to be as less intrusive as possible as I don't know the codebase.