-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
I’m trying to consume inventory events from Kafka, but it currently takes a considerable amount of time to unmarshal or decode the event data. To improve this, I suggest exposing the internal event API externally. This would allow consumers to more easily decode the event data without the need for heavy unmarshaling on their side.
The relevant code here: inventory-api/event.go
By making this change, we can streamline the event consumption process and improve performance for consumers.
Acceptance criteria
- I can use the data schema to decode the event defined from the kafka event
- account is impacted by
-
ACM-15034 As a global hub engineer, I can run e2e tests so that I can know the inventory-api is running normally w/o acm
- Closed
- clones
-
RHCLOUD-36260 add a new optional field called cluster_reason
- Code Review
- is cloned by
-
RHCLOUD-36299 Align Resource ID Definitions Between Eventing API and Inventory API
- Closed