squakez commented on issue #593:
URL: https://github.com/apache/camel-k-runtime/issues/593#issuecomment-772591895
@lburgazzoli that's correct, the default is that path. I was thinking that
if one has a specific need, he can edit the integration definition by setting a
concrete `mountPath`. For example:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: resources-route-edited
namespace: default
spec:
resources:
- content: the file body
name: resources-data.txt
type: data
mountPath: /tmp/my-edited-path/
sources:
- content: |
// camel-k: language=groovy
from('timer:resources')
.routeId('resources')
.setBody()
.simple("resource:classpath:resources-data.txt")
.log('file content is: ${body}')
name: resources-route.groovy
```
```
kubectl apply -f integration-edited.yaml
integration.camel.apache.org/resources-route-edited created
...
kubectl exec -it resources-route-edited-86dc56d46f-sz4b4 -- cat
/tmp/my-edited-path/resources-data.txt
the file body
```
The same should apply to any binary file. Also here, that path will be
included in your application classpath, but it can be useful if a file is
expected to be in any particular place. @makandre, hope that helps.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
