Feature/dlq requeue#67
Merged
Merged
Conversation
llambeau
force-pushed
the
feature/dlq-requeue
branch
3 times, most recently
from
2c977fd to
b084e4e
Compare
Instead of pushing directly to a destination queue, the requeue mechanism now publishes messages to the configured exchange using a routing key. This lets exchange bindings determine the target queue(s), following the normal message routing flow. - Replace destinationQueue param with routingKey in API - Configure shovel with dest-exchange and dest-exchange-key - Enable add-forward-headers for message traceability - Update tests and webspicy schemas Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
llambeau
force-pushed
the
feature/dlq-requeue
branch
from
b084e4e to
cb108e6
Compare
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
1 participant
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.
No description provided.