lsergio commented on issue #5164:
URL: https://github.com/apache/camel-k/issues/5164#issuecomment-1952965043
@lburgazzoli I'm working around this with the following strategy:
* Created the config maps for each file:
```
apiVersion: v1
data:
data: file1 contents
kind: ConfigMap
metadata:
name: cm1
---
apiVersion: v1
data:
data: file1 contents
kind: ConfigMap
metadata:
name: cm2
```
And mounted them like this:
```
traits:
mount:
resources:
- configmap:cm1@/etc/camel/resources/file1.txt
- configmap:cm2@/etc/camel/resources/file2.txt
```
Then the Integration references the files as:
`{{RESOURCES_DIR}}/file1.txt/data`
where RESOURCES_DIR is /etc/camel/resources
My goal was to use only `{{RESOURCES_DIR}}/file1.txt`, but still be able to
use separate cms for each file, due to the size constraints.
In my case we're creating an IDE-like frontend where our users would input
their integration code and config files, so using the classpath is not an
option.
--
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
