Add support for messageId, correlationId, and type in RabbitMQ bindings #3661
+58
−0
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.
Description
This pull request introduces several enhancements to the RabbitMQ bindings and metadata utilities. The most important changes involve adding new utility functions to extract specific metadata fields and updating the RabbitMQ publishing functions to utilize these new utilities.
Enhancements to metadata utilities:
metadata/utils.go
: AddedTryGetMessageId
,TryGetCorrelationId
, andTryGetType
functions to extractmessageId
,correlationId
, andtype
from metadata properties, respectively. [1] [2]Updates to RabbitMQ bindings:
bindings/rabbitmq/rabbitmq.go
: Modified theInvoke
method to extract and setMessageId
,CorrelationId
, andType
from the request metadata using the new utility functions.pubsub/rabbitmq/rabbitmq.go
: Updated thepublishSync
method to extract and setContentType
,MessageId
,CorrelationId
, andType
from the request metadata using the new utility functions.Issue reference
Please reference the issue this PR will close: #3650
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: