Support for disabling consumers using an application config

[golevelup]

Support for disabling consumers using an application config

[WonderPanda]

At first I thought that you simply wanted to disable all RabbitMQ behavior for certain instances of your application. If this were the case, you can just conditionally build up your imports array based on an environment/config variable and exclude the call to RabbitMQModule.forRoot/forRootAsync.

Since you also want to be able to still interact with the AmqpConnection to be able to publish messages however, this would require some tweaking to the library.

I don't see a problem with adding in an additional configuration option that will allow you to control whether or not handlers get attached to RabbitMQ though since I can see this being a common use case that will come up. It shouldn't be a large change, I'll try to get a new package version pushed this week

[WonderPanda]

@theabuitendyk This feature is now available in version 1.10.0

[theabuitendyk]

Thanks for your help @WonderPanda!

[priyankinfinnov]

Is there a way to register dynamically on the fly @WonderPanda @theabuitendyk ?

Context: I am writing a e2e/integration test for a distributed system. And i want to hold the queue consumer for some time. So i can use registerHandlers flag but when i want them to be executed how do i register dynamically via code?

[WonderPanda]

@priyankinfinnov You can inject the AmqpConnection and interact directly with it to register subscriptions/rpc etc