quarkus-infinispan extension hard-coding location of hotrod-client.properties

I posted this on zulip chat last week but haven’t been able to get a response (https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Quarkus.20infinispan.20extension.20hotrod-client.2Eproperties/near/222425566)

Using the Infinispan component with camel-k. The issue is that the quarkus-infinispan extension hard-codes the location of hotrod-client.properties as META-INF/hotrod-client.properties (https://github.com/quarkusio/quarkus/blob/master/extensions/infinispan-client/deployment/src/main/java/io/quarkus/infinispan/client/deployment/InfinispanClientProcessor.java#L62).

In camel-k, the build is performed by the operator, so the user has no way to put hotrod-client.properties within a META-INF directory. The user just submits an Integration custom resource (https://gist.github.com/edeandrea/770c84be9da204ff0b13f2340975904e#file-camelk-client-yml-L56-L57) referencing a ConfigMap, and that ConfigMap is mounted in a directory in the running pod and is added to the root of the classpath. Because of this, as a camel-k user using the camel-infinispan component (which the underlying runtime is quarkus, handing off to the quarkus-infinispan extension), the integration just doesn’t work.

This has been cross-posted on the camel-k issue tracker as well (apache/camel-k#1898)

[karesti]

@wburns IMO, on top of that, we should be able to override any property of the client Infinispan without using the hotrod-client.properties as we do in SB

[wburns]

I personally like option 1 so that any app can set default values for the client properties without having to use the hotrod-client.properties file.