[💡 FEATURE REQUEST]: Allow setting routing_key dynamically when publishing a job to a pipeline

[rauanmayemir]

Plugin

JOBS

I have an idea!

Currently we specify all the AMQP parameters in the pipeline config like so:

jobs:
  pipelines:
    my_amqp_pipeline:
      driver: amqp
      config:
        prefetch: 10
        priority: 1
        durable: true
        queue: my_amqp_queue_1
        exchange: amqp.direct
        exchange_durable: true
        routing_key: my_amqp_queue_1
        requeue_on_fail: true

On the spiral side, I can only specify my_amqp_pipeline pipeline name as a destination options (alongside delay, but it's irrelevant). It would make sense for basic setup, but AMQP usually requires two parameters: exchange name and routing key.

In my case it's just a 'direct' exchange with underlying queues bound by name, i.e a single exchange but lots of my_amqp_queue_1, my_amqp_queue_2, my_amqp_queue_3. Other use cases of rabbitmq could also involve fanouts, where I could be sending a wildcard pattern as a routing key destination.

It would be nice to be able to dynamically specify custom routing_key on the spiral side (with a fallback to default routing_key in the pipeline config). E.g:

/** @var QueueInterface $queue */
$queue->push(
    JobPayload::class,
    $payload,
    (new Options())
        ->onQueue('my_amqp_pipeline')
        // would fallback to `my_amqp_queue_1` as per config if not set, i.e null
        ->withRoutingKey('my_amqp_queue_3')
        ->withDelay(20)
);