-
Notifications
You must be signed in to change notification settings - Fork 27
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
ConfigValidationException on Quarkus 3.7.1 #231
Comments
how do you set the properties? |
Those two are set as environment variables. |
nothing was changed in vault. must have been in smallrye config. I saw something similar with |
Probably related with quarkusio/quarkus#38479. If this is a blocker for you, please use any of the alternatives described in quarkusio/quarkus#38479 (comment) Quarkus 3.7.2 just came out with a relaxed validation. Alternatively, you can update SmallRye Config manually for Quarkus 3.7.1: <dependency>
<groupId>io.smallrye.config</groupId>
<artifactId>smallrye-config-common</artifactId>
<version>3.5.4</version>
</dependency>
<dependency>
<groupId>io.smallrye.config</groupId>
<artifactId>smallrye-config-core</artifactId>
<version>3.5.4</version>
</dependency> |
the issue seems to be related to we actually just checked that using |
Is this still an issue? @computerlove did you try with Quarkus 3.7.2? Thanks! |
Yeah, tried today. Same problem. |
Hi, we ran into a similar issue using Quarkus 3.7.3 and quarkus-vault 3.4.1
Configuration properties also injected via env variables. Went back to Quarkus 3.6.9 for the moment. |
Yeah, still there in 3.7.3. |
have you tried using |
Ok, thanks for checking. I'll have a look. |
Removing
|
Can you please provide me with the full configuration you are using for Vault and how is being set up exactly? Please remove any sensitive information, but keep the configuration keys. Thanks! |
In application.properties we have quarkus.vault.kv-secret-engine-mount-path=kv
quarkus.vault.secret-config-kv-path=ext/databaseandotherthings,app/applicationname When deploying a container this is set as enviroment:
|
Thanks! |
If you run with |
Correct :) |
Great. Please use that for now until I figure out something. |
I've added a fix, but I'll probably prefer to only ship it in the next major Quarkus version. Is it acceptable to have |
When upgrading to Quarkus 3.7.1 (and quarkus-vault 3.4.1) the application crash at startup with
The text was updated successfully, but these errors were encountered: