christophd opened a new pull request, #13078:
URL: https://github.com/apache/camel/pull/13078

   # Description
   
   - Pipes may reference a Knative broker as a source/sink. 
   - Properly configure the Knative component endpoint URI 
(knative:event/my-event-type?kind=Broker&name=default) on the resulting route 
definition when the Pipe uses a Knative broker reference
   
   Example Pipe:
   ```yaml
   apiVersion: camel.apache.org/v1
   kind: Pipe
   metadata:
     name: timer-event-source                  
   spec:
     source:
       ref:
         kind: Kamelet
         apiVersion: camel.apache.org/v1
         name: timer-source
       properties:
         message: "Hello world!"
     sink:
       ref:
         kind: Broker
         apiVersion: eventing.knative.dev/v1
         name: foo-broker
       properties:
         type: org.apache.camel.event.foo
   ```
   
   - Make sure to always use Locale.ENGLISH when performing schema validation 
in YAML DSL unit tests (avoids assertion errors due to internationalized error 
messages when tests are run on a machine with different default Locale set e.g. 
GERMAN)
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (note that 
Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch)
   
   # Tracking
   
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   Fixes CAMEL-20403
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [x] I have run `mvn clean install -DskipTests` locally and I have 
committed all auto-generated changes
   


-- 
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]

Reply via email to