You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "lance (via GitHub)" <gi...@apache.org> on 2023/03/03 02:13:44 UTC

[GitHub] [camel-k] lance commented on issue #3668: Kamelet CloudEvents set `source` attribute to the string "source"

lance commented on issue #3668:
URL: https://github.com/apache/camel-k/issues/3668#issuecomment-1452846931

   Just following up here so that the issue doesn't get closed, and to provide what is my current workaround for this issue. When creating a Knative `Trigger`, I inject CloudEvent `source` and `type` headers using the following steps in the `KameletBinding`.
   
   ```yaml
   apiVersion: camel.apache.org/v1alpha1
   kind: KameletBinding
   metadata:
     name: telegram-source-binding
   spec:
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1alpha1
         name: telegram-source
       properties:
         authorizationToken: API_TOKEN_HERE
     steps:
     - ref:
         apiVersion: camel.apache.org/v1alpha1
         kind: Kamelet
         name: insert-header-action
       properties:
         name:  CamelCloudEventSource
         value: org.apache.camel.event.telegram
     - ref:
         apiVersion: camel.apache.org/v1alpha1
         kind: Kamelet
         name: insert-header-action
       properties:
         name:  CamelCloudEventType
         value: telegram.message
     sink:
       ref:
         kind: Broker
         apiVersion: eventing.knative.dev/v1
         name: default
   ```
   
   This works fine, but it would be nice to have reasonable defaults so that the yaml can be as simple as possible.
   
   
   
   


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org