Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport for the Header Exchange trigger binding #71
Conversation
This comment has been minimized.
This comment has been minimized.
msftclas
commented
Sep 27, 2019
•
|
|
|
|
||
| if (!string.IsNullOrWhiteSpace(arguments)) | ||
| { | ||
| var argumentObject = JObject.Parse(arguments); |
This comment has been minimized.
This comment has been minimized.
ianrathbone
Sep 27, 2019
Author
I shall hold my hands up and confess here that I wasn't sure on the best way to pass in the header arguments in order to pass them to QueueBind as a Dictionary. Any advice here would be appreciated!
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.
ianrathbone commentedSep 27, 2019
One of the concepts supported by RabbitMQ is the "Headers Exchange".
You can read more on this here: https://www.rabbitmq.com/tutorials/amqp-concepts.html
This pull request modifies the existing binding to add support for specifying an exchange instead of a queue. In the RabbitMQ Service this will create a queue based on the exchange name and bind based on specified x-match headers with supplied arguments.
I'm looking to use this in an upcoming project that relies heavily on this methodology, by spinning up several functions that will listen to their own specific headers independently of each other.
I appreciate the work you have done so far and look forward to seeing how I can help extend the functionality of this extension!