lburgazzoli commented on issue #3501: URL: https://github.com/apache/camel-k/issues/3501#issuecomment-1201125464
> Probably a silly question but isn't this what the [Service Binding Operator](https://github.com/redhat-developer/service-binding-operator) was suppose to do ? Or is this just a better way of achieving binding ? Thanks! Right is it quite similar and I was thinking about the SBO when writing the issue, however I found that it is not that easy to use SBO for generic resources and in the context of KameletBinding as you may need to have knowledge about the resource that exposes the information and the consumer and with my probably outdated knowledge of SBO what it would be required is: - to annotate the Binding and Bucket resource - to annotate the kamelet binding for the correct mapping So the main goal here is to make it possible for kamelet developers to define how the mapping between resources should be done, regardless of how the binding is performed so i.e. the camel-k operator could generate any SBO metadata/resource to materialize the binding or it can go it's way if the SBO operator is not present. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
