fedmsg is deprecated - Fedora infrastructure messages now available via AMQP
Hello folks,
Over the last several months, Fedora Infrastructure has been working
towards migrating away from fedmsg (ZeroMQ, on which it is based). As of
last week, the Fedora AMQP message broker is available outside the
infrastructure network. If you're currently consuming the ZeroMQ
messages published by Fedora via fedmsg or any other ZeroMQ client,
please look into migrating to AMQP as the ZeroMQ endpoint will
eventually be shut down. Until that occurs, all messages are available
via both AMQP and ZeroMQ.
For folks using Python, a fedmsg replacement library and command-line
interface have been written called "fedora-messaging". This package is
available on PyPI, in Fedora 29+, and is also available in the Fedora
Infrastructure repositories for EPEL7 and Fedora 28. Library and CLI
documentation is available online[0]. Documentation specifically for
consuming messages from the public AMQP broker is available at
https://fedora-messaging.readthedocs.io/en/stable/fedora-broker.html
If you are *not* using Python, or if re-inventing wheels is something
you enjoy, you can receive these messages using the AMQP client library
of your choice: https://www.rabbitmq.com/devtools.html has a number of
clients in various languages listed.
This is a new service and library, so there are bound to be a few
hiccups along the way. Please report any issues you encounter with the
broker on the infrastructure list, and any issues with the library or
the documentation on the issue tracker[1] (or the infrastructure list if
you don't have a GitHub account) and we'll make sure they're addressed
as soon as possible.
[0] https://fedora-messaging.readthedocs.io/en/stable/index.html
[1] https://github.com/fedora-infra/fedora-messaging/issues
Regards,
Jeremy