Any ideas on disabling property expansion in kamel run?

[barius]

The use case is that I'm trying to log to different files in each pod on environment variable HOSTNAME. In application.properties :

quarkus.log.file.enable=true
quarkus.log.file.path=/log/log.test-logging.${HOSTNAME}

Kamel does this expansion on kamel run and ${HOSTNAME} is resolved to my local machine rather than k8s pod name.

Since Quarkus also provides property expression/expansion, could there be any method or thoughts to differentiate the two? e.g. changing prefix and postfix of "github.com/magiconair/properties" or add a switch to disable it?

Regards :)

[squakez]

Maybe you can leverage directly Camel properties features: https://camel.apache.org/components/3.17.x/properties-component.html#_using_system_and_environment_variables_in_locations

[barius]

@squakez If I use Camel properties, should I pass the properties via kamel run -p? Or --trait camel.properties=?

[barius]

-t camel.properties='quarkus.log.file.path=/log/log.test-logging.${HOSTNAME}' works :)
Now that the log file is distinct per pod. Thanks!

Also, how to pass multiple properties this way? Multiple -t camel.properties= seems to not work, and -t camel.properties=[foo=bar,baz=blabla] won't work :(

[squakez]

You can both use a properties file or pass a list of properties. The kamel run will replace into trait for you. Ie:

test.properties
a=x
b=y
...
kamel run Test.java -o yaml -p file:test.properties

and

kamel run Test.java -o yaml -t camel.properties=a=x -t camel.properties=b=y

will produce the same output.

[barius]

yep, -p and -t camel.properties are interchangeable unless property expansion is involved, since the Go package github.com/magiconair/properties used in camel-k does some shallow parsing to -p properties.
Anyway this is no big issue and I can use some wrapper script to pass a property file as multiple -t camel.properties arguments :P

[squakez]

I was answering to:

Multiple -t camel.properties= seems to not work, and -t camel.properties=[foo=bar,baz=blabla] won't work :(

the way to use multiple properties via trait is the one provided in the previous comment.

[barius]

yes, I have tried again and multiple -t camel.properties= is now OK.
Now I use a wrapper script to expand a properties file into several -t camel.properties= args and it's ok.
Shall we close this issue?