squakez opened a new pull request #1965: URL: https://github.com/apache/camel-k/pull/1965
<!-- Description --> With this PR we include the possibility to use `BinaryData` in `ConfigMap`s, leaving any encoding/decoding to the k8s platform. The decision of the using `BinaryData` vs `Data` is based on the sniffed `mime-type` of the resource passed. In order to maintain the possibility to explicit encode we have the following situations: 1. `kamel run ... --resource file.text` --> will leverage `Data` `ConfigMap`, mounting a volume with a plain text data file. 2. `kamel run ... --resource file.binary`-->will leverage `BinaryData` `ConfigMap`, mounting a volume with a binary data file. 3. `kamel run ... --resource file.text/file.binary --compression` --> will leverage `Data` `ConfigMap`, we base64 encode the content, mounting a volume with a base64 encoded file. Decoding will be up to the application logic. Close #1946, fix #1881 <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note feat(trait): leverage ConfigMap binary data for resources ``` ---------------------------------------------------------------- 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
