I am trying to consume the CentOS related messages from the Fedora Message bus.
And I noticed that Fedora and CentOS send different types of messages for the same events
Here is an example: random message from the org.fedoraproject.prod.buildsys.tag
org.fedoraproject.prod.buildsys.tag
https://apps.fedoraproject.org/datagrepper/v2/id?id=39b84434-aade-4c73-a7d1-139383144b59&is_raw=true&size=extra-large
has header
"fedora_messaging_schema": "koji_fedoramessaging.tag.TagV1"
The CentOS message for the similar event in the org.centos.prod.buildsys.tag topic https://apps.fedoraproject.org/datagrepper/v2/id?id=ce1530b9-7b57-496b-a710-e441b1fc47e7&is_raw=true&size=extra-large
org.centos.prod.buildsys.tag
"fedora_messaging_schema": "base.message"
This is not a blocking issue as consumer apps can be tweaked to handle base-type of messages. But It would be nice to have consistent approach to messaging, so that CentOS consumers can also benefit from the detailed messaging schemas, as defined in:
https://github.com/fedora-infra/koji-fedoramessaging-messages/blob/main/koji_fedoramessaging_messages/tag.py
hey @bookwar . As it's Stream infra related , would you mind creating a ticket on the Jira CS tracker ? Stream team doesn't track this public infra tracker (dedicated for everything but stream infra) See https://wiki.centos.org/ReportBugs.html (that was announced some time ago but creating in correct tracker would make it visible for the stakeholders/platform owners)
Thanks
Filed https://issues.redhat.com/browse/CS-2195
Metadata Update from @bookwar: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.