[Messenger] send using the routing_key for AMQP transport #28955
Conversation
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
This was referenced Oct 22, 2018
gregurco
approved these changes
Oct 23, 2018
sroze
approved these changes
Oct 25, 2018
43dbc5f to
666d2d9
Compare
|
(rebased on 4.1) |
|
Thank you @nicolas-grekas. |
sroze
added a commit
that referenced
this pull request
Oct 25, 2018
…(nicolas-grekas) This PR was merged into the 4.1 branch. Discussion ---------- [Messenger] send using the routing_key for AMQP transport | Q | A | ------------- | --- | Branch? | master | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #28133 | License | MIT | Doc PR | - Shouldn't we publish using the routing_key that is used by the listening queue? Commits ------- 666d2d9 [Messenger] send using the routing_key for AMQP transport
Merged
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.
Shouldn't we publish using the routing_key that is used by the listening queue?