Vincent Sevel

how do you set the properties?

nothing was changed in vault. must have been in smallrye config. I saw something similar with `export QUARKUS_VAULT_AUTHENTICATION_CLIENT_TOKEN=...` not working anymore any idea @radcortez ?

the issue seems to be related to `QUARKUS_VAULT_AUTHENTICATION_APP_ROLE_ROLE_ID` being interpreted as `quarkus.vault.authentication.app.role.role.id`, whereas the property is `quarkus.vault.authentication.app-role.role-id`. we actually just checked that using `QUARKUS_VAULT_AUTHENTICATION_CLIENT-TOKEN` instead of `QUARKUS_VAULT_AUTHENTICATION_CLIENT_TOKEN` worked (at least...

have you tried using `QUARKUS_VAULT_AUTHENTICATION_CLIENT-TOKEN` ?

should that be a separate extension then?

yes there is a [destroy](https://www.vaultproject.io/api-docs/secret/kv/kv-v2#destroy-secret-versions) operation (kv v2). do you want to try out creating a PR @ps-burgstaller ?

I will start looking at it this week

interesting draft, thanks. can you explain the logic behind `getLongestMatchingMountPathPrefix`? when we have `quarkus.vault.secret-config-kv-path."shared.kafka"`, what is the convention for `shared.kafka`? `shared` is supposed to be a mount path prefix? we...

I am wondering if this should be: ``` quarkus.vault.secret-config-kv-path."shared"."kafka"=kafka quarkus.vault.secret-config-kv-path."app1"."db"=db ``` or: ``` quarkus.vault.secret-config-kv-path."shared:kafka"=kafka quarkus.vault.secret-config-kv-path."app1:db"=db ``` instead of: ``` quarkus.vault.secret-config-kv-path."shared.kafka"=kafka quarkus.vault.secret-config-kv-path."app1.db"=db ``` in `"shared.kafka"` , it is not clear that...

this would work: ``` quarkus.vault.secret-config-kv-path."mykvv1/v1"=bar quarkus.vault.kv-secret-engine-mount-path.mykvv1=secret-v1 ``` in that case, in `VaultConfigSource` : ``` private Map fetchSecrets(String path, String prefix) { Map secretJson = getVaultKVSecretEngine().readSecretJson(path).await().indefinitely(); ``` we have `prefix=mykvv1/v1`. we...