-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed
Labels
Milestone
Description
Description
Following the implementation of the Vault guide (https://quarkus.io/guides/vault) generates serialization error in native mode at runtime, stacktrace attached.
As a workaround, I added the following reflection-config.json
:
[
{
"name" : "io.quarkus.vault.runtime.client.dto.VaultAppRoleAuthBody",
"allDeclaredConstructors" : true,
"allPublicConstructors" : true,
"allDeclaredMethods" : true,
"allPublicMethods" : true,
"allDeclaredFields" : true,
"allPublicFields" : true
},
{
"name" : "io.quarkus.vault.runtime.client.dto.VaultAppRoleAuthAuthMetadata",
"allDeclaredConstructors" : true,
"allPublicConstructors" : true,
"allDeclaredMethods" : true,
"allPublicMethods" : true,
"allDeclaredFields" : true,
"allPublicFields" : true
}
]
Steps to reproduce the behavior
- Follow the guide: https://quarkus.io/guides/vault
mvn package -Pnative
- Run the native runner
Configuration
quarkus.vault.url=https://my-vault.onkubernetes.intranet
quarkus.vault.tls.skip-verify=true
quarkus.vault.authentication.app-role.role-id=******
quarkus.vault.authentication.app-role.secret-id=******
quarkus.vault.kv-secret-engine-version=2
quarkus.vault.secret-config-kv-path=apps/sample/config
Environment
- OS
Linux xxxxxx 5.3.0-23-generic Entity Manager injection support #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - Java
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode) - GraalVM
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-20191008104205.buildslave.jdk8u-src-tar--b07)
OpenJDK 64-Bit GraalVM CE 19.2.1 (build 25.232-b07-jvmci-19.2-b03, mixed mode) - Quarkus version
1.0.0.CR2