Extending Kombu/Celery

[mdomans]

Problem

I'm looking at an issue for which I'd like to have multiple RabbitMQ queues receiving data from single RabbitMQ exchange using the hash exchange plugin. This plugin is de facto part of RabbitMQ now, just usually disabled. I wanted to describe this topology using Kombu primitives in Python so that individual team members don't have to configure RabbitMQ locally or remotely for work.

My questions:

• Is there a way in Kombu handle discovery of capabilities provided by broker? Not all devs will have this plugin enabled so I'd like to handle that gracefully or show meaningful error.
• Is there a way in Kombu to describe certain feature needs, for example, RabbitMQ plugin enabled and force that or show error if impossible (e.g. user lacks permission to enable plugin)
• Provided all that - what is the correct way to describe, for example, 4 queues bound to one exchange and at which point during Celery startup it should be done?

[open-collective-bot[bot]]

Hey @mdomans 👋,
Thank you for opening an issue. We will get back to you as soon as we can.
Also, check out our Open Collective and consider backing us - every little helps!

We also offer priority support for our sponsors.
If you require immediate assistance please consider sponsoring us.