squakez commented on PR #15063: URL: https://github.com/apache/camel/pull/15063#issuecomment-2284079844
I made some test with some binary file, and it does not throw any exception. The presence of any binary file would be parsed normally, although it would not be probably something useful to have into app properties. The exception throwing is a generic one provided in all file IO signatures. However, this is something that should not be expected. In order to enable this feature, the op team needs to mount any given secret/configmap in the application pod in a given folder (ie, /etc/camel/conf.d/_configmaps) and enable the parsing via setting `camel.main.cloud-properties-location= /etc/camel/conf.d/_configmaps` setting. I'd expect they mount the binary certificate under any different location if they don't want the property to be scanned as an application properties. Anything they are eventually mounting in those folders is because they want the runtime to scan as a property. -- 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
