-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
from version 1.11.0 Vault MicroProfile Config Source stopped working #14707
Comments
/cc @vsevel |
do you have the logs by any chance? |
yes thanks! the full log is:
|
not sure. and I am not familiar with the dev mode. the vault extension should print some logs. I guess it fails to run before we try to fetch |
@vsevel But the strangest thing about all this is that it work fine with version 1.10.5, but just changing to 1.11.0 fails |
is the application running fine in normal mode (i.e. not in dev mode)? |
ok, i could already run it in normal mode! |
so it is probably related to how dev mode is initializing the app. one difference is that the vault extension was moved to the boostrap phase in 1.11 #13498. this might be the reason why it was still working in 1.10. |
all this means that somebody have to move the vault extension in next versions? |
@radcortez could you try to help @vsevel figure this out? |
sure, I'll have a look |
The issue is actually related with the Dev Console. Since the Config Dev Console is done at build time, the Vault ConfigSource is not available at that point, and the expansion fails. I've added a fix in #14309 to move the Dev Console Config to Runtime. This approach is also more correct, since it displays all values in the runtime configs and not only build time. Until the fix is not applied, as a workaround, you can set an empty default value with |
thank you for the alternative solution Roberto! |
I'm a bit worried about this. Won't we slow down dev mode significantly if we start doing all sorts of things with the Dev UI before it's even accessed? /cc @stuartwdouglas |
In this case, I think we are fine. The configuration has to be loaded anyway for the application. Potentially, we may have a slowdown if a Lets not forget, that currently the values we see in the console may not be correct, since they only take account the build sources, a value may be overridden in a runtime source we won't see that reflected in the console. |
and the issue certainly applies to all config sources that are fetching properties at runtime, which is then very limiting. |
Describe the bug
from version 1.11.0 Vault MicroProfile Config Source stopped working to use vault with Databases (Vault MicroProfile Config Source) and OIDC
Expected behavior
quarkus fetched vault kv values first and then try verificted dependent properties. In version 1.10.5 works fine, but in 1.11.0 (and 1.11.1) does not work
Actual behavior
on startup throw error:
To Reproduce
in a new application in version 1.11.0 or 1.11.1 add vault, quarkus-reactive-pg-client, quarkus-resteasy, quarkus-resteasy-mutiny, quarkus-oidc, quarkus-vertx dependencies in appplication.properties add the following properties:
Configuration
Environment (please complete the following information):
uname -a
orver
: Linux 5.3.18-lp152.60-default x86_64 x86_64 x86_64 GNU/Linuxjava -version
: OpenJDK 64-Bit Server VM Corretto-11.0.10.9.1 (build 11.0.10+9-LTS, mixed mode)mvnw --version
orgradlew --version
): 3.6.3The text was updated successfully, but these errors were encountered: