lsergio commented on issue #5164:
URL: https://github.com/apache/camel-k/issues/5164#issuecomment-1953054287
@lburgazzoli Now I got your point.
I tested it like this:
Config Maps:
```
apiVersion: v1
data:
file1.txt: "{\"name\": firstName}"
kind: ConfigMap
metadata:
name: cm1
---
apiVersion: v1
data:
file2.txt: "{\"name\": lastName}"
kind: ConfigMap
metadata:
name: cm2
```
And the Integration:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: myintegration
spec:
sources:
- name: main.yaml
language: yaml
content: |-
- from:
uri: "rest:POST:/test"
steps:
- to:
uri:
"jsonata:/file1.txt?inputType=JsonString&outputType=JsonString"
- to:
uri: "log:info"
traits:
logging:
level: DEBUG
ingress:
enabled: false
knative-service:
enabled: false
mount:
resources:
- configmap:cm1
- configmap:cm2
```
The files were still mounted at different directories:
k exec -it myintegration-74d7fdd854-cfbqw -- ls -R /etc/camel/resources
```
/etc/camel/resources:
cm1 cm2
/etc/camel/resources/cm1:
file1.txt
/etc/camel/resources/cm2:
file2.txt
```
but reading them from the classpath worked fine.
So, for components that can load classpath-based resources, this works fine.
The use case would then be components that eventually do not support so.
Thanks for the support.
--
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
