-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistently support "cloudEventsType" property in Pipes source/sink #5577
Labels
Milestone
Comments
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 6, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 6, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 7, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 10, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
christophd
added a commit
to christophd/camel-k
that referenced
this issue
Jun 10, 2024
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirement
Consistently support property settings on both source and sink in Pipes when connecting with a Knative broker.
Problem
When a Pipe references a Knative broker as a sink users are able to specify the CloudEvents event type using the
cloudEventsType
property setting. This controls the event type that is produced by the Pipe.On the source side when the Pipe consumes the event stream from a Knative broker users need to use
type
property setting instead. This filters the event stream for events of a given type.The different names of properties is misleading and we should consistently support the same settings on both source and sink when connecting with the Knative broker.
Proposal
No response
Open questions
No response
The text was updated successfully, but these errors were encountered: