[GitHub] [camel-k] nicolaferraro commented on issue #1676: kamelets: source/sink binding

[GitBox <gi...@apache.org>]

nicolaferraro commented on issue #1676:
URL: https://github.com/apache/camel-k/issues/1676#issuecomment-683799191


   Can we have something like this instead:
   
   ```yaml
   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: twitter-directmessage-source
   spec:
     configuration:
       key: value
       user: my-user
       password: just-provide-it-in-plain-text-for-now
     source:
       ref:
         apiVersion: camel.apache.org/v1alpha1
         kind: Kamelet
         name: twitter-directmessage
     sink:
       ref:
         apiVersion: messaging.knative.dev/v1alpha1
         kind: InMemoryChannel
         name: twitter
   ```
   
   There are multiple reasons:
   - The configuration I propose is compatible with the JSON schema exposed by the Kamelet definition (so it can be validated), while the array of configuration items is not
   - We currently don't support per-property secret entries iirc, but only global secrets and it seems not easy to create them now, considering also that kamelet properties are locally scoped
   
   Wdyt @lburgazzoli ?


----------------------------------------------------------------
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:
users@infra.apache.org