[FEATURE REQUEST] Documentation for more than one routingKey

[gustajz]

Hi everyone

It's possible add support to documenting an exchange that contains more than one routingKey for different queues?

Proposal Example:

channels:
  user/signedup:
    bindings:
      amqp:
        is: routingKey
        key:
        - name: key1
          queue:
            name: my-queue-name
            durable: true
            exclusive: true
            autoDelete: false
            vhost: /
        - name: key1
          queue:
            name: my-queue-name
            durable: true
            exclusive: true
            autoDelete: false
            vhost: /
        exchange:
          name: myExchange
          type: topic
          durable: true
          autoDelete: false
          vhost: /

Below is a real world example:

Thanks!

[fmvilas]

If I understood correctly, you can already do this:

channels:
  push/enviar-push-polling/message: # Note that slashes are converted to dots when using AMQP.
    bindings:
      amqp:
        is: routingKey
        queue:
          name: push.enviar-push-polling.queue
          durable: true
          exclusive: true
          autoDelete: false
          vhost: /
        exchange:
          name: myExchange
          type: topic
          durable: true
          autoDelete: false
          vhost: /
  push/enviar-push/message: # Note that slashes are converted to dots when using AMQP.
    bindings:
      amqp:
        is: routingKey
        queue:
          name: push.enviar-push.queue
          durable: true
          exclusive: true
          autoDelete: false
          vhost: /
        exchange:
          name: myExchange
          type: topic
          durable: true
          autoDelete: false
          vhost: /

Let me know if this makes sense to you.

[fmvilas]

I'm closing this issue but feel free to comment if you think it's not solved. Thanks.