Add command to transfer delayed messages from one broker to another#1765
Merged
Conversation
9e41781 to
6fa0582
Compare
irinascurtu
approved these changes
Apr 7, 2026
Member
|
Are there any tests we can/should be adding? |
Member
Author
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. |
a76da88 to
c1ab8bb
Compare
This was referenced Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a
delays transfercommand 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.