-
Notifications
You must be signed in to change notification settings - Fork 3k
Make YAML configuration work for Bootstrap Config #10070
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
Conversation
|
@geoand it looks safe enough for a backport, WDYT? |
|
@gsmet yeah, it's completely safe |
...rc/main/java/io/quarkus/deployment/builditem/AdditionalBootstrapConfigProviderBuildItem.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I added a minor suggestion as an attempt to make it more typesafe, but feel free to ignore :)
...n/java/io/quarkus/deployment/builditem/AdditionalBootstrapConfigSourceProviderBuildItem.java
Show resolved
Hide resolved
|
@geoand This doesn't cover custom We use a custom one to merge multiple yaml files (from maven submodules) that also contain |
|
@famod no it does not. But this PR was only for bootstrap config anyway, not for build-time config. |
|
Ah, now I understand. Thanks! |
|
👍 |
Fixes: #9973
The idea here to allow an extension to register which
ConfigSourceProvidercan work in Bootstrap Config, because we (correctly) don't do auto-discovery when building the Bootstrap Config