Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Sending Raw Messages #102

Closed
ghost opened this issue Jul 18, 2019 · 0 comments
Closed

Allow Sending Raw Messages #102

ghost opened this issue Jul 18, 2019 · 0 comments

Comments

@ghost
Copy link

ghost commented Jul 18, 2019

When processing a message sent from one service ("original sending bus") to another ("original destination") fails, the message is marked as poison and, if configured, will end up in a special "dead letter queue" ("dlq").

We would like to be able to consume those messages and re-send them to their "original destination" - meaning - re-enqueueing them into their original destination queue.

Currently, when sending a message, Grabbit is setting headers that match the sending bus.

In order to restore the original flow, we need to add an "impersonation" ability, by adding headers that match to the original sending bus.

Meaning, allowing setting the headers manually - by allowing to send raw messages.

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

No branches or pull requests

1 participant