-
Notifications
You must be signed in to change notification settings - Fork 599
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
Delivery Format: support specifying the event format #8057
Comments
Maybe even a delivery spec field spec:
delivery:
format: input|structured|binary|null |
@pierDipi I've updated this issue to be more generic (just sending structured events from the delivery spec), and I'll open individual sub issues to add support for this |
@pierDipi should we have a feature flag for this? |
Would we than start to track what we actually received? currently we accept binary/structure, but dispatch via binary due to reasons. For |
@matzew the current idea is to add a new CE extensions to the events at ingress which indicated the format we received them in See for example #8076 |
I think if we keep the current behavior (e.g. we emit as But, perhaps that can lead to side effects? 🤔 |
So, I'd go just But I guess just |
Problem
Currently, when dispatching an event, we generally send it in the binary event format. However, to integrate with some systems (such as AWS EventBridge) we will need to be able to support sending events in structured format.
To support this, we are going to add a new field to the
Delivery
spec of resources, which will look like:If set to
binary
, then the component would deliver the event in binary format. If set tostructured
, then the component would deliver the event in structured format. If set toingress
, then the component would send the event in the format that the broker received it.Persona:
Which persona is this feature for?
System integrators
Exit Criteria
An e2e test for each resource that supports the delivery spec that verifies that the event was received in structured format.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
10 days
Additional context (optional)
The text was updated successfully, but these errors were encountered: