Marvin Bredal Lillehaug

When building the model the information about annotations on the argument and its parameters are merged. ArgumentCreator: ```java public Optional createArgument(Operation operation, MethodInfo methodInfo, short position) { //methodInfo = java.util.List...

Ok, I will wait for your work on #740.

Updated to versions 1.8.1 and 2.0.0.RC10

As far as I see it should'nt be a big task to fix. Not sure if the above fix/hack is the correct place to handle this. It would be nice...

Those two are set as environment variables.

Yeah, tried today. Same problem. But did not have time to test the config for disable the validation and investigate. Will try to take another look tomorrow.

Yeah, still there in 3.7.3. Running with `quarkus.config.mapping.validate-unknown=false` for now.

Removing `quarkus.config.mapping.validate-unknown=false` and changing to `...ROLE-ID` and `...SECRET-ID` resulted in ``` unknown authType null java.lang.RuntimeException: Failed to start quarkus at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source) at io.quarkus.runtime.Application.start(Application.java:101) at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:111) at io.quarkus.runtime.Quarkus.run(Quarkus.java:71) at io.quarkus.runtime.Quarkus.run(Quarkus.java:44)...

`UnsupportedOperationException: unknown authType null` with `QUARKUS_VAULT_AUTHENTICATION_APP-ROLE_ROLE-ID` and `QUARKUS_VAULT_AUTHENTICATION_APP-ROLE_SECRET-ID` also. In application.properties we have ```properties quarkus.vault.kv-secret-engine-mount-path=kv quarkus.vault.secret-config-kv-path=ext/databaseandotherthings,app/applicationname ``` When deploying a container this is set as enviroment: ``` QUARKUS_VAULT_URL: "$VAULT_URL" QUARKUS_VAULT_AUTHENTICATION_APP-ROLE_ROLE-ID:...

Correct :)