Closed vsevel closed 7 months ago
for your information also @aloubyansky
@vsevel We can do that, once if I can resolve the issues in laid out in #215 (i.e., SSL & proxy config)
I checked this is fixed in 4.0.0-alpha.2
see also https://github.com/quarkiverse/quarkus-vault/pull/215
The vault extension config source blocks the application from restarting in dev mode (when vault itself is not running using devservice).
To reproduce:
start vault:
start the application:
force restart the application with:
s
. This fails with:Tracing the code I can see in the
VertxVaultClient
, in:Funny enough
send.await().indefinitely().bodyAsString()
works and returns the appropriate response from vault. The error seems related toUniFailOnTimeout$UniFailOnTimeoutProcessor
trying to schedule a task.At this point the vault client is an instance of
PrivateVertxVaultClient
.Progressing using the debugger, I was able once to get it to run, as if there was a race condition on the initialization of the executor.
Not too sure at this point if this is a vault extension issue, or a quarkus issue. upon restart the vault extension should be provided with a non terminated executor. you opinion @radcortez at the same time, if the config source was using a pure jdk http client, we would not be bothered by this type of issue. what do you think @kdubb ?
see https://github.com/vsevel/reproducer_vault_devservices