Skip to content

Conversation

@ikavgo
Copy link
Contributor

@ikavgo ikavgo commented May 17, 2025

Proposed Changes

Further extend queue types registry and other parts to allow adding new queue types via plugins.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

Checklist

Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally with my changes
  • If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
  • If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

Further Comments

@ikavgo ikavgo requested a review from michaelklishin May 17, 2025 18:50
@ikavgo ikavgo force-pushed the ik-queues-with-plugins branch from b9b6dfb to bcdb0b7 Compare May 17, 2025 21:33
@michaelklishin michaelklishin added this to the 4.2.0 milestone May 19, 2025
@michaelklishin michaelklishin merged commit eb7634c into main May 19, 2025
273 checks passed
@michaelklishin michaelklishin deleted the ik-queues-with-plugins branch May 19, 2025 02:22
LoisSotoLopez added a commit to cloudamqp/rabbitmq-server that referenced this pull request Aug 1, 2025
We are moving the functionality of getting the nodes/members of an
amqqueue from the `amqqueue` module to `rabbit_amqqueue`. This goes in
the line of previous PRs work towards reducing direct access to the
`QueueTypeState`, such as
rabbitmq#13905. Also, we will
need to discretize different formats of the `nodes` entry in the
`QueueTypeState`, to support both the previous one as a list of nodes
and the new one as a map of nodes to Ra UIds. Doing so in a module such
as `amqqueue`, which feels like an accessor module around the `amqqueue`
record, doesn't feel right.
LoisSotoLopez added a commit to cloudamqp/rabbitmq-server that referenced this pull request Aug 13, 2025
We are moving the functionality of getting the nodes/members of an
amqqueue from the `amqqueue` module to `rabbit_amqqueue`. This goes in
the line of previous PRs work towards reducing direct access to the
`QueueTypeState`, such as
rabbitmq#13905. Also, we will
need to discretize different formats of the `nodes` entry in the
`QueueTypeState`, to support both the previous one as a list of nodes
and the new one as a map of nodes to Ra UIds. Doing so in a module such
as `amqqueue`, which feels like an accessor module around the `amqqueue`
record, doesn't feel right.
LoisSotoLopez added a commit to cloudamqp/rabbitmq-server that referenced this pull request Sep 29, 2025
We are moving the functionality of getting the nodes/members of an
amqqueue from the `amqqueue` module to `rabbit_amqqueue`. This goes in
the line of previous PRs work towards reducing direct access to the
`QueueTypeState`, such as
rabbitmq#13905. Also, we will
need to discretize different formats of the `nodes` entry in the
`QueueTypeState`, to support both the previous one as a list of nodes
and the new one as a map of nodes to Ra UIds. Doing so in a module such
as `amqqueue`, which feels like an accessor module around the `amqqueue`
record, doesn't feel right.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants