Vincent Sevel
Vincent Sevel
something like this: ``` quarkus.vault.kv-secret-engine."myengine".version=1 quarkus.vault.kv-secret-engine."myengine".mount-path=secret-v1 quarkus.vault.kv-secret-engine."myengine".secret-config-kv-path=bar quarkus.vault.kv-secret-engine."myengine".secret-config-kv-path."foo"=myfoo ``` this would be much clearer.
I think we could also simplify `VaultKvManager` by keeping maps of kv1 and kv2, and assume that if the key is null or `'default'` this is the default kv, and...
hello. I created https://github.com/quarkiverse/quarkus-vault/pull/411 do you need multiple mount path support in the context of the vault config source, or for the different crud operations? at the moment I only...
Fixed by https://github.com/quarkiverse/quarkus-vault/pull/411
great effort. out of curiosity, have you got native tests running in CI against drools running quarkus?
great news! hello, when will this be a in a release?
for the `standbyok` parameter, it is going to be difficult to test. however I was able to demonstrate the issue @wiebeck is reporting using the `sealedcode` parameter (which we don't...
Did you have a look @kdubb ?
hello @wiebeck can you go ahead and squash/rebase your commits. unless there last minute comments, I think we can go ahead. thanks for your patience.
thanks @wiebeck