squakez commented on PR #6158: URL: https://github.com/apache/camel-k/pull/6158#issuecomment-2876557182
Ok, I got your point. The "problem" is that the plain runtime is not aware of where it is running (it could not be necessarily on a cloud environment), so, it must be instructed specifically where to look for by setting the following camel property `camel.component.properties.location=file:/tmp/my.properties`. You can add multiple locations and, ideally, you can combine the possibility to mount the configmap in a given location togheter with this property. In that case the runtime will be able to parse the file properly. We can think to add something on Camel core, in order to be able to automatically parse any file with `.properties` in `camel.main.cloud-properties-location` similarly of what the Camel K runtime is doing. I suggest you to report on [main Camel project](https://issues.apache.org/jira/projects/CAMEL/issues) in order to be widely discussed with the community. -- 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
