-
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
Warn about unknown application config files #35298
Conversation
radcortez
commented
Aug 9, 2023
- Fixes warn or fail if an application.yaml is provided without the quarkus-config-yaml dependency #13227
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
reflectiveClass.produce(ReflectiveClassBuildItem.builder(URI.class).constructors(true).build()); | ||
// No need to include the application files, because they don't change | ||
if (!launchModeBuildItem.getLaunchMode().isDevOrTest()) { | ||
configRecorder.unknownConfigFiles(); |
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.
So you want to log it once at build time and one at runtime, right?
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.
Yes, because this also looks into the config
folder and quarkus.config.locations
, which may be different from build to runtime, so we need to perform the checks twice.
core/deployment/src/main/java/io/quarkus/deployment/steps/ConfigGenerationBuildStep.java
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |