squakez commented on issue #6157:
URL: https://github.com/apache/camel-k/issues/6157#issuecomment-2862358630
> 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)](https://github.com/apache/camel-k/pull/6128) 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
