Support for the Header Exchange trigger binding #71
Conversation
|
|
|
|
||
| if (!string.IsNullOrWhiteSpace(arguments)) | ||
| { | ||
| var argumentObject = JObject.Parse(arguments); |
There was a problem hiding this comment.
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!
|
Thank you for sending this! We'll provide some feedback on the PR as soon as possible @jeffhollan can you please comment on the scenario? The issue is #69 if you want to move the discussion there. |
|
Apologies about the lack of response here. @jeffhollan / @dariagrigoriu can you please comment on the functionality? |
|
Pinging here as we have been resuming work on this extension. We don't create non-existent queues anymore like we used to, could you rebase and comment on how this functionality might fit in with the existing model ? |
|
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
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!