Allow passive exchange and queue declaration about reactor-rabbitmq HOT 8 CLOSED

This is certainly something that can be done. As a workaround for now, it's possible to try to re-declare the queue, with the exact same arguments. Resource declaration is idempotent in AMQP, as long as the properties of the resource are the same. Trying to re-declare an existing resource with different properties will result in an error.

from reactor-rabbitmq.

@acogoluegnes Sorry for the delay, but yes this is exactly what we wanted. Thanks very much for the prompt enhancement!

from reactor-rabbitmq.

@acogoluegnes I have a feature branch ready, can we discuss the PR on gitter?

from reactor-rabbitmq.

You can create the PR (or draft PR) and we can discuss there. I'll be available on Gitter on Monday. Thanks!

from reactor-rabbitmq.

Fixed by #88.

from reactor-rabbitmq.

@fridgebuzz There is now an example test that uses passive declaration before publishing messages, can you please confirm this is what you want to achieve?

from reactor-rabbitmq.

Hi team, can I active/ inactive exchange at runtime?

from reactor-rabbitmq.

@sureshparmar042 Exchanges in RabbitMQ cannot disabled, they can only be deleted and re-created. Note after deletion, all their bindings are deleted as well.

from reactor-rabbitmq.