cfitzw commented on PR #6158: URL: https://github.com/apache/camel-k/pull/6158#issuecomment-2873022560
Correct, and setting `camel.main.cloud-properties-location` explicitly does work. - When using plain-quarkus and providing a **generic** configmap (non file-based), it is already automatically setting this cloud location and the properties are able to be read successfully. - Even if this configmap is **file-based**, it still auto-sets the location, it is just unaware that it needs to parse the configmap a bit differently. The default runtime currently has awareness of how to handle this scenario, somehow, as it works (as shown in these tests). What I am questioning is why similar logic can't be used to auto-handle this scenario. -- 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
