Skip to content
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

Invalid warning on quarkus.vault.secret-config-kv-path."prefix" property #13276

Closed
vsevel opened this issue Nov 13, 2020 · 0 comments · Fixed by #13300
Closed

Invalid warning on quarkus.vault.secret-config-kv-path."prefix" property #13276

vsevel opened this issue Nov 13, 2020 · 0 comments · Fixed by #13300
Labels
area/vault kind/bug Something isn't working
Milestone

Comments

@vsevel
Copy link
Contributor

vsevel commented Nov 13, 2020

Describe the bug
Using property secret-config-kv-path."prefix" works as expected, but prints an invalid warning at startup:

WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.vault.secret-config-kv-path.singer" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo

Expected behavior
There should be no warning

To Reproduce
Execute IT VaultMultiPathConfigITCase in the core project

Additional context
I am not sure if this is something that is specific to the vault configuration, because I don't see the same behavior on ConfiguredBeanTest that is using ConfiguredBeanTest with property public Map<String, List<String>> stringListMap with values:

# And list form
quarkus.rt.all-values.string-list-map.key1=value1,value2,value3
quarkus.rt.all-values.string-list-map.key2=value4,value5
quarkus.rt.all-values.string-list-map.key3=value6
@vsevel vsevel added the kind/bug Something isn't working label Nov 13, 2020
@ghost ghost added the area/vault label Nov 13, 2020
@ghost ghost added this to the 1.11 - master milestone Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vault kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant