quarkus: Regression: Various YAML configuration issues in 1.6.1.Final

Please allow me to skip the issue-template for this since it has already been taken care of in smallrye-config 1.8.5 which Quarkus should update to ASAP when that version is released. See:

C&P of two manifestion of those problems:

11:36:10,778 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[2]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,778 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[1]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,778 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[4]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,778 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[3]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[5]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.protocols.[1]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.protocols.[0]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.log.category.liquibase.changelog.ChangeSet.level" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.log.category.com.somecompany.someproject.middleware.level" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo
11:36:10,779 WARN  [io.qua.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.ssl.cipher-suites.[0]" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo

Those .[x]-warnings are actually false negatives but the loglevel related warnings are correct.

Temporary Workaround: Add this to your Maven dependencyManagement, before quarkus-bom or quarkus-universe-bom:

<dependency>
    <groupId>io.smallrye.config</groupId>
    <artifactId>smallrye-config-source-yaml</artifactId>
    <version>1.8.1</version>
</dependency>

/cc @radcortez @geoand @gsmet

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 3
  • Comments: 21 (20 by maintainers)

Most upvoted comments

Note that I will be a bit nervous to upgrade SmallRye Config post CR1 so let’s try to get this in before CR1 please.

@geoand already did.

These issues are localised only in the YAML Config Source, so it is easy to workaround by downgrading to the last dependency like stated by @famod without affecting the configuration core.

All the reported issues are already fixed in SmallRye Config and just require a release and minor bump in the Quarkus dependency.

@famod Thank you for all the help and report!