You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@kamilmysliwiec sorry I didn't notice your answer, the concern is as @jarPotato states it that I still want to be able to send messages, I just want to disable the processing.
Currently our workaround is that we gathered all listeners/processors classes in a single module, that is imported conditionally based on an environment variable.
The issue with this pattern is that it's quite easy to accidentally import a listener/processor in the wrong module (or fail to catch this in a review), and thus have the wrong instances (web instead of workers) process the jobs.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
In our architecture, we have two types of "applications", that share the same code:
We would like to be able disable job processing on some instances only.
Describe the solution you'd like
In
BullModule.forRoot
method, have adisabled
prop, to disable the processing of jobs on this instance.Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Be able to easily disable processing.
The text was updated successfully, but these errors were encountered: