Support for disabling consumers using an application config

I have many instances of my application running, some of which I’d like to consume from RabbitMQ queues and others that should be dedicated to serving API requests.

I’m using the RabbitSubscribe decorator on a service method to connect a consumer.

@RabbitSubscribe({
    exchange: 'exampleExchange.created',
    routingKey: 'exampleExchange.*',
    queue: 'exampleExchange.created',
  })
  public async process(event): Promise<void> {
    ...
  }

Is there a way to stop this from consuming from the queue based on my application config, while allowing the application to publish to the same exchanges/queues?

[WonderPanda]

@theabuitendyk This feature is now available in version 1.10.0

[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