-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[Messenger] Multiple failed transports #15177
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
[Messenger] Multiple failed transports #15177
Conversation
weaverryan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! Several small things - wonderful start!
|
@weaverryan should we put a warning or something that this was introduced on symfony 5.3? Or it is not needed. |
OskarStark
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small comments from my side
f3ae9ed to
d784895
Compare
|
Hugo, thanks a lot for contributing these docs ... and congrats on your first Symfony Docs contribution 🎉 What a great first contribution! Cheers! Oskar, we added the |
|
Thanks a lot for the help! |
New Feature: Messenger: Multiple Failure Transports Transports
closes #15168
This PR adds the documentation related to PR: symfony/symfony#38468
What it needs to be clear in the documentation:
failure_transportconfigured the messages will be discardedfailure_transportconfiguration, the one taken into account is at the transport level configuration.--transport. Without arguments is the global failed transport taken into account.