Argo claims to be CloudEvent-compliant but doesn't support ingesting cloudevent anywhere

[vnzongzna]

Is your feature request related to a problem? Please describe. The ingestion controllers discard any metadata present in the event received & create their own cloud event instance for every message/event to be used between eventsource->eventbus->sensors. This makes it impossible to actually keep track of the actual source that sends the event.

Describe the solution you'd like A minimum validation/check to see if the data that is sent is cloudevent compliant or not. If it is, no need to re-generate the fields that exist already in the event.

Describe alternatives you've considered Haven't considered any alternatives yet.

Additional context We have one SNS that can be subscribed by any other team (internally) & they use an SDK that we provide to specify the sns arn behind the scenes. In argo events, we always get the source as the same SNS, the time as the one when we actually received the message. Both of these fields can be specified with the SDK that we offer & can be used to actually monitor the actual event details correctly.

---

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.