-
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
"Unrecognized configuration key" regression in 1.11.0.CR1 #14233
Comments
/cc @geoand |
@gsmet do you know anything about this one? |
+1 |
@vsevel @matthyx btw, Final release is planned for tomorrow morning so this is a bit time sensitive. Building master with the PR reverted should be relatively easy by following: https://github.com/quarkusio/quarkus/blob/master/CONTRIBUTING.md#checking-an-issue-is-fixed-in-master . |
/cc @radcortez as it might also be a SmallRye Config regression. |
@vsevel could you also try without the runtime provided config file? Trying to narrow things down. |
@gsmet we are going to try. there might be some challenges in rebuilding master in our corporate env. |
@vsevel also a couple of additional questions:
|
|
OK, so if building master is complex for you, maybe try with the 2 experiments:
and let's discuss things from there. |
the quarkus build fails on gradle on our env. there is no knowledge on this. so it is probably not going to work out. if you can provide a debug version of quarkus we can use, that will be easier for us. I tried moving all "quarkus" properties to the build time file (I left our applicative properties). and that did not resolve the issue. |
@vsevel also can you iterate through the 1.11 Betas and see which one introduces the issue? |
I removed the runtime config entirely, and I still see the warnings. I will go through the betas. good idea. |
Having a look as well. |
I have the issue with Beta2. trying with beta1. |
I have the issue with beta1. is it related to having a bootstrap config? if so #13498 was part of beta1. and that might explain why the vault properties were not subject to the warnings? |
Yes, it was an issue with bootstrap config |
@stuartwdouglas well done! |
Found some problems like this one quarkusio/quarkus#14233 for quarkus.log.category."xxxx".min-level, so upgrade the version to fix
Describe the bug
When running in native mode with 1.11.0.CR1, we get "Unrecognized configuration key" warnings on a list of properties.
those properties are all "quarkus" properties (we do not have any warnings on our applicative properties).
some of those properties come from src/main/resources/application.yml, some properties come from runtime provided "application.yml", and some properties are not set at all in any of these 2 files.
We do not have this behavior in 1.10.5 native, or 1.11.0.CR1 jvm.
The interesting thing is that the program is running normally. that is those properties are correctly read from the config.
Expected behavior
No warnings "Unrecognized configuration key" in native mode.
Actual behavior
here is what we get at startup:
From all of these properties we have 3 cases:
properties coming from src/main/resources/application.yaml
which is all quarkus properties, except:
properties coming from runtime provided application.yaml
which is all quarkus properties except vault properties:
properties not coming from our config either runtime or build time
To Reproduce
We tried to reproduce in a simple "getting started" example, but did not succeed (instead we stumbled upon #14229).
so unfortunately we do not have a reproducer.
I tried printing a few variables at startup (some coming from src/main/resources/application.yml, and some coming from the runtime provided application.yml):
in jvm mode I get (which is expected):
in native mode I get the same values, but with the unexpected warnings, such as:
so properties are read appropriately (which explains why the program is running normally). the only issue seems to be those invalid warnings.
The text was updated successfully, but these errors were encountered: