If for any reason the RabbitMQ instance is wiped and the queues are lost, there is nothing to recreate the MessageQueueTrigger queues, this causes data to be lost.
Ideally when a queue is gone, Fission or KEDA should redeclare it. Another possible solution is for the userworker service to include the queue in its reconciliation loop.
If for any reason the RabbitMQ instance is wiped and the queues are lost, there is nothing to recreate the MessageQueueTrigger queues, this causes data to be lost.
Ideally when a queue is gone, Fission or KEDA should redeclare it. Another possible solution is for the userworker service to include the queue in its reconciliation loop.