Contrib.social

Unable to provide queue or exchange configuration when using dotted naming convention

Open on Drupal.org →
Created on 23 March 2023, over 1 year ago
Updated 5 February 2024, 11 months ago

Problem/Motivation

Configuration can be used to provide settings per queue and/or exchange. However, since the configuration key is used to indicate the queue/exchange name, it is impossible to use a dotted naming convention.

Steps to reproduce

  1. Add a queue in RabbitMQ with the name "foo.bar"
  2. In rabbitmq.config.yml define configuration for the queue:
    queues:
  foo.bar:
    arguments: { }
    auto_delete: false
    durable: true
    exclusive: false
    nowait: false
    passive: false
    routing_keys: {  }
    ticket: null
  3. Try to import the configuration and notice that the exception "foo.bar key contains a dot which is not supported." is thrown

Proposed resolution

Add a name property to the configuration for both the rabbitmq.exchange and rabbitmq.queue, and use the value of the name property to determine the configuration for a specific exchange/queue.

A queue can than be configured using:

queues:
  -
    arguments: { }
    auto_delete: false
    durable: true
    exclusive: false
    name: 'foo.bar'
    nowait: false
    passive: false
    routing_keys: {  }
    ticket: null

Remaining tasks

  • Get reviews

User interface changes

N.a.

API changes

N.a.

Data model changes

Name property is added for the configuration of exchanges and queues.

🐛 Bug report
Status

Downport

Version

4.0

Component

Code

Created by

🇳🇱Netherlands watergate

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024