Sounds good so we don't break on restart. On Wed, 9 Oct 2019 at 10:26, Aurelien Bompard <aurelien@xxxxxxxxxxx> wrote: > > Hey folks, > > The fedora-messaging consumers are currently subscribed to the amq.topic exchange where they get all messages sent over AMQP. However, the bridges that forward messages from fedmsg publish to the zmq.topic exchange, therefore consumers need to subscribe to that one too to benefit from the bridges. > It's just a matter of changing the rabbit/queue role, which should always have had that double binding in place. It is not necessary to update every consumer's config file. If the app did not have an issue with this missing binding until now, it means it's not consuming from unmigrated fedmsg messages, and it does not need an ansible run to fix it. Otherwise running the playbook will add the missing bindings. > > What do you think? > > Aurélien > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
