Skip to content

Add command to transfer delayed messages from one broker to another#1765

Merged
bording merged 5 commits into
masterfrom
migrate-delayed-messages
Apr 7, 2026
Merged

Add command to transfer delayed messages from one broker to another#1765
bording merged 5 commits into
masterfrom
migrate-delayed-messages

Conversation

@bording

@bording bording commented Apr 4, 2026

Copy link
Copy Markdown
Member

This PR adds a delays transfer command to the transport command line tool that can transfer delayed messages from one broker to another.

It requires that both a source and destination connection string be specified so that the command can connect to both of the broker instances.

The documentation for the new command can be found here.

@bording bording force-pushed the migrate-delayed-messages branch from 9e41781 to 6fa0582 Compare April 6, 2026 22:50
@bording bording changed the title Add command to migrate delayed messages from one broker to another Add command to transfer delayed messages from one broker to another Apr 6, 2026
@bording bording marked this pull request as ready for review April 6, 2026 22:54
@andreasohlund

Copy link
Copy Markdown
Member

Are there any tests we can/should be adding?

@bording

bording commented Apr 7, 2026

Copy link
Copy Markdown
Member Author

Are there any tests we can/should be adding?

I pulled all the shared code between the two commands into a helper class. There was already a test around the logic of creating a new routing key for the messages, which is probably the part of the code that is the most critical to have a test around.

I have run the new command locally to verify it works, but we don't currently have the required test infrastructure to fully run the commands in an automated test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants