-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to disable MP ConfigProperties and ConfigMapping #20275
Comments
I'm not totally sure if we should add this. Can you please elaborate more on a concrete use case? Thanks! |
In my use case I have several profiles that we will call
Is-it clear now? |
If I remember correctly, |
@radcortez If it allows to do the same thing that the test I have in my PR, it would be great |
Reopening, to close only when linked PR is merged. |
Description
Up to now, if we want to ease the mapping of the configuration, we can rely on the annotations
@ConfigProperties
from MicroProfile Config and/or@ConfigMapping
from SmallRye Config. If used, Quarkus will check at runtime that the corresponding properties are available in the configuration which can be a problem if this part of the configuration only makes sense for production but not for the tests.Implementation ideas
The idea could be to rely on build time conditions to enable or not the annotations
@ConfigProperties
and/or@ConfigMapping
.The text was updated successfully, but these errors were encountered: