Quarkus shows warning messages for properties that are actually used but not part of config classes
See original GitHub issueDescribe the bug It seems like the big config PR removed he list of false positives keys that wouldn’t trigger a warning when set.
Expected behavior
Setting -Dquarkus.profile
(as is mentioned for example here) should not trigger the logging of any warning.
Actual behavior
Setting -Dquarkus.profile
yields:
2019-12-06 11:48:32,749 WARN [io.qua.config] (main) Unrecognized configuration key "quarkus.profile" was provided; it will be ignored
To Reproduce
- Use any of the Quarkus quickstarts (from the
development
branch). - Build
- Run with
-Dquarkus.profile
set
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (15 by maintainers)
Top Results From Across the Web
Configuration Reference Guide - Quarkus
In this reference guide we're going to describe various aspects of Quarkus configuration. A Quarkus application and Quarkus itself (core and extensions) are ......
Read more >All configuration options - Quarkus
AWS Lambda Type Default
AWS Lambda Common Type Default
AWS Lambda Gateway REST API Type Default
Agroal ‑ Database connection pool Type Default
Read more >Mapping configuration to objects - Quarkus
The Server interface is able to map configuration properties with the name server.host into the Server.host() method and server.port into Server.port() ...
Read more >Contexts and Dependency Injection - Quarkus
In such case, it's possible to exclude types and dependencies from the bean discovery. The quarkus.arc.exclude-types property accepts a list of string values ......
Read more >Configuring Your Application - Quarkus
The @Inject annotation is not necessary for members annotated with @ConfigProperty . If the application attempts to inject a configuration property that is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The second solution seems more intuitive to me.
Who wants to take this after #5989 is in? If no one wants to, I can do it