Available Schemas

These are the topics that you can expect to see on Fedora’s message bus, sorted by the python package that contains their schema. Install the corresponding python package if you want to make use of the schema and access additional information on the message you’re receiving.

In the Fedora Infrastructure, some of those topics will be prefixed by org.fedoraproject.stg. in staging and org.fedoraproject.prod. in production.

anitya-schema

You can view the history of all anitya messages in datagrepper.

  • org.release-monitoring.prod.anitya.distro.add: Message sent by Anitya to the “anitya.distro.add” topic when a new distribution is added. (history)
  • org.release-monitoring.prod.anitya.distro.edit: Message sent by Anitya when a distribution is edited. (history)
  • org.release-monitoring.prod.anitya.distro.remove: Message sent by Anitya when a distribution is removed. (history)
  • org.release-monitoring.prod.anitya.project.add: The message sent when a new project is created in Anitya. (history)
  • org.release-monitoring.prod.anitya.project.edit: The message sent when a project is edited in Anitya. (history)
  • org.release-monitoring.prod.anitya.project.flag: Sent when a new flag is created for a project. (history)
  • org.release-monitoring.prod.anitya.project.flag.set: Sent when a flag is closed for a project. (history)
  • org.release-monitoring.prod.anitya.project.map.new (history)
  • org.release-monitoring.prod.anitya.project.map.remove (history)
  • org.release-monitoring.prod.anitya.project.map.update (history)
  • org.release-monitoring.prod.anitya.project.remove: The message sent when a project is deleted in Anitya. (history)
  • org.release-monitoring.prod.anitya.project.version.remove (history)
  • org.release-monitoring.prod.anitya.project.version.update (history)
  • org.release-monitoring.prod.anitya.project.version.update.v2 (history)

bodhi-messages

You can view the history of all bodhi messages in datagrepper.

  • bodhi.buildroot_override.tag: Sent when a buildroot override is added and tagged into the build root. (history)
  • bodhi.buildroot_override.untag: Sent when a buildroot override is untagged from the build root. (history)
  • bodhi.compose.complete: Sent when a compose task completes. (history)
  • bodhi.compose.composing: Sent when the compose task composes. (history)
  • bodhi.compose.start: Sent when a compose task starts. (history)
  • bodhi.compose.sync.done: Sent when a compose task sync is done. (history)
  • bodhi.compose.sync.wait: Sent when a compose task sync is waiting. (history)
  • bodhi.errata.publish: Sent when an errata is published. (history)
  • bodhi.repo.done: Sent when a repo is created and ready to be signed or otherwise processed. (history)
  • bodhi.update.comment: Sent when a comment is made on an update. (history)
  • bodhi.update.complete.stable: Sent when an update is available in the stable repository. (history)
  • bodhi.update.complete.testing: Sent when an update is available in the testing repository. (history)
  • bodhi.update.edit: Sent when an update is edited. (history)
  • bodhi.update.eject: Sent when an update is ejected from the push. (history)
  • bodhi.update.karma.threshold.reach: Sent when an update reaches its karma threshold. (history)
  • bodhi.update.request.obsolete: Sent when an update is requested to be obsoleted. (history)
  • bodhi.update.request.revoke: Sent when an update is revoked. (history)
  • bodhi.update.request.stable: Sent when an update is submitted as a stable candidate. (history)
  • bodhi.update.request.testing: Sent when an update is submitted as a testing candidate. (history)
  • bodhi.update.request.unpush: Sent when an update is requested to be unpushed. (history)
  • bodhi.update.requirements_met.stable: Sent when all the update requirements are meant for stable. (history)
  • bodhi.update.status.testing.koji-build-group.build.complete: Sent when an update is ready to be tested. (history)

copr-messaging

You can view the history of all copr messages in datagrepper.

  • copr.build.end: schema for the old fedmsg-era ‘copr.build.end’ message (history)
  • copr.build.start: schema for the old fedmsg-era ‘copr.build.start’ message (history)
  • copr.chroot.start: Schema for the old fedmsg-era ‘copr.chroot.start’ message, this message duplicated the ‘copr.build.start’ message, so you should never use this. (history)
  • build.end (history)
  • build.start (history)
  • chroot.start (history)

fedocal-messages

You can view the history of all fedocal messages in datagrepper.

  • fedocal.calendar.clear: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a calendar is cleared. (history)
  • fedocal.calendar.delete: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a calendar is deleted. (history)
  • fedocal.calendar.new: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a calendar is created. (history)
  • fedocal.calendar.update: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a calendar is updated. (history)
  • fedocal.calendar.upload: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when meetings have been uploaded into the calendar. (history)
  • fedocal.meeting.delete: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a meeting is deleted. (history)
  • fedocal.meeting.new: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a meeting is created. (history)
  • fedocal.meeting.reminder: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a reminder is sent. (history)
  • fedocal.meeting.update: A sub-class of a Fedora message that defines a message schema for messages published by fedocal when a meeting is updated. (history)

fedora-elections-messages

You can view the history of all fedora_elections messages in datagrepper.

  • fedora_elections.candidate.delete: A sub-class of a Fedora message that defines a message schema for messages published by Elections when a candidate is deleted. (history)
  • fedora_elections.candidate.edit: A sub-class of a Fedora message that defines a message schema for messages published by Elections when a candidate is edited. (history)
  • fedora_elections.candidate.new: A sub-class of a Fedora message that defines a message schema for messages published by Elections when a new candidate is added. (history)
  • fedora_elections.election.edit: A sub-class of a Fedora message that defines a message schema for messages published by Elections when an election is edited. (history)
  • fedora_elections.election.new: A sub-class of a Fedora message that defines a message schema for messages published by Elections when a new election is created. (history)

fedora-messaging-the-new-hotness-schema

You can view the history of all hotness messages in datagrepper.

  • org.fedoraproject.prod.hotness.update.bug.file: Message sent by the-new-hotness to “hotness.update.bug.file” topic when bugzilla issue is filled. (history)
  • org.fedoraproject.prod.hotness.update.drop: Message sent by the-new-hotness to “hotness.update.drop” topic when update is dropped. (history)

fedora-planet-messages

You can view the history of all planet messages in datagrepper.

  • org.fedoraproject.prod.planet.post.new: The message sent when a new post is published in planet. (history)

fedorainfra-ansible-messages

You can view the history of all ansible messages in datagrepper.

  • ansible.playbook.complete: Defines the message that is sent when an Ansible Playbook completes (history)
  • ansible.playbook.start: Defines the message that is sent when an Ansible Playbook starts (history)
  • git.receive: Defines the message that is sent when an Ansible Playbook starts (history)

mdapi-messages

You can view the history of all mdapi messages in datagrepper.

  • mdapi.repo.update: A sub-class of a Fedora message that defines a message schema for messages published by mdapi when a repo’s info is updated. (history)

noggin-messages

You can view the history of all fas messages in datagrepper.

  • fas.group.member.sponsor: The message sent when a user is added to a group by a sponsor (history)
  • fas.user.create: The message sent when a user is created (history)
  • fas.user.update: The message sent when a user is updated (history)

nuancier-messages

You can view the history of all nuancier messages in datagrepper.

  • nuancier.new: A sub-class of a Fedora message that defines a message schema for messages published by nuancier when a new thing is created. (history)

pagure-messages

You can view the history of all pagure messages in datagrepper.

  • pagure.Test.notification: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.commit.flag.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.commit.flag.updated: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.git.branch.creation: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.git.branch.deletion: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.git.receive: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.git.tag.creation: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.git.tag.deletion: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.group.edit: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.issue.assigned.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.assigned.reset: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.comment.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.dependency.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.dependency.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.drop: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.edit: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is updated. (history)
  • pagure.issue.new: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.issue.tag.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.issue.tag.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when an issue is deleted. (history)
  • pagure.project.deleted: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.edit: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.forked: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.group.access.updated: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.group.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.group.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.new: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.tag.edited: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.tag.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.user.access.updated: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.user.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.project.user.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.assigned.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.assigned.reset: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.closed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.comment.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.comment.edited: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.flag.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.flag.updated: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.initial_comment.edited: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.new: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.rebased: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.reopened: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.tag.added: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.tag.removed: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)
  • pagure.pull-request.updated: A sub-class of a Fedora message that defines a message schema for messages published by pagure when a new thing is created. (history)