-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
Unset
-
None
-
-
-
Major
While attempting to decode events by the [eventing api](https://github.com/project-kessel/inventory-api/blob/main/internal/eventing/api/event.go#L23), I encountered the following error
`json: cannot unmarshal number into Go struct field ResourceMetadata.metadata.id of type string`
This issue arises because the [resource ID in the eventing API](https://github.com/project-kessel/inventory-api/blob/main/internal/eventing/api/event.go#L23) differs from the [resource ID in the inventory API](https://github.com/project-kessel/inventory-api/blob/main/api/kessel/inventory/v1beta1/resources/metadata.pb.go#L31)
This PR aligns the definitions of `resource ID` in both APIs to ensure compatibility and resolve the encoding/decoding issue
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-36298 Improve Event Consumption by Exposing Internal Event API Externally
- New
- is cloned by
-
RHCLOUD-36300 The Kafka deletion event for the relationship does not differ from the defined Kafka event
- New
-
RHCLOUD-36301 The Event API's relationship schema is inconsistent with the definition
- New