nicolaferraro opened a new issue #2080: URL: https://github.com/apache/camel-k/issues/2080
Suppose that I want to create a Kamelet that uses [this component](https://camel.apache.org/components/latest/google-storage-component.html) under the hood. The component accepts a parameter that is a path that points to some credentials provided as a JSON file by the cloud provider (all Google cloud components behave the same). Obviously this does not map 1:1 with the current Kamelet model, but I wonder how can we make it fit. Should we change the component to accept the credentials directly (is it possible?), or make something different? E.g. we can use a parameter of "type" = "binary" that may indicate this scenario The CLI + operator can make sure the parameter is e.g. expected to be passed encoded (b64?) in a KameletBinding and the property `{{myparam}}` can evaluate to the file location at runtime. This seems a bit too custom as solution. Do you see a better one? cc: @squakez , @astefanutti , @lburgazzoli , @oscerd , @davsclaus , @christophd Should we instead define a general encoding of KameletBinding parameters into secrets, so that all properties are eventually stored into files and we can get `{{theparam}}` value, or `{{file:theparam}}` file? ---------------------------------------------------------------- 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
