Capability of supporting incident / failure exchanges and queues should be optional

Is this a BUG REPORT or FEATURE REQUEST

• BUG Report
• Feature request

What happened

Currently, every micro-service creates a delayed MQ exchange of itself. This is used only in case of incident / failure messages. If a service does does not want to use this feature, they are still required to install the delayed-exchange plugin on their Rabbit MQ instance.

What you expected to happen

This plugin should be required only if the service wants to use the feature.

How to solve it (as minimally and precisely as possible)

1. Let the service switch ON / OFF this feature from configuration. Default can ON (to support backward capability)
2. Create Delayed exchanges only if this flag is ON
3. Bind to incident queues only if this flag is ON
4. Publish incident messages only if this flag is ON

Anything else we need to know?

NA

Environment

• @apifie/node-microservice version :
• NodeJS version (node -v) :
• npm version (npm -v) :
• Others
  • Database (MySQL) version
  • Message Queue (MQ) version
  • Cache (Redis) version
  • Others : xxxxx