Values from file-based ConfigMaps are not available as properties with plain-quarkus

[cfitzw]

What happened?

When mounting a file-based configmap, using the plain-quarkus runtime, the associated values from the ConfigMap are not made available as properties.

This is only true when using the plain-quarkus runtime and works as expected with the default runtime as of v2.6.

Steps to reproduce

1. Create a file-based ConfigMap
2. Pull in the ConfigMap into the integration
3. Attempt to reference a property:

# file: app.properties
my-variable=result

kubectl create configmap my-configmap --from-file=app.properties

# camel-k: config=configmap:my-configmap

- from:
    uri: "timer:tick?period=1000"
    steps:
      - setBody:
          simple: "{{my-variable}}"
      - to: "log:info"

Relevant log output

Camel K version

v2.6

[cfitzw]

This may or may not be related, but if using the standard .properties ${} placeholder syntax, camel k is unable to resolve these... meaning using {{base.fqdn}} in an integration fails.

# file: app.properties
base.env=dev
base.domain=domain.com
base.fqdn=cluster-${base.env}.${base.domain}

[squakez]

About the generic question, I've provided an answer in #camel-k > ✔ Camel K Quarkus ConfigMap Properties @ 💬

[squakez]

This may or may not be related, but if using the standard .properties ${} placeholder syntax, camel k is unable to resolve these... meaning using {{base.fqdn}} in an integration fails.

file: app.properties

base.env=dev
base.domain=domain.com
base.fqdn=cluster-${base.env}.${base.domain}

Specifically to this one, this is because Camel K in this case is using a "pre-made" generic build, so the app.properties file variable are not recalculated as it would happen when you build it from source. In version 2.7.0 we're introducing a build from source (via git project) which should resolve this situation. In any case, you'd be needing to build it from source anyway in order to calculate (and embed into the jar) the properties file.