#97: Make receive-message match sqs behaviour #106
Merged
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
SQS only includes message attributes if they are specified in the recieve message request, while ElasticMQ was returning all attributes by default. I have updated the ReceiveMessageDirective to respect the messageAttributeName parameter and to no longer include attributes unless specified.
Member
|
Released in 0.13.4. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This resolves issue #97
SQS only includes message attributes if they are specified in the receive message request, while ElasticMQ was returning all attributes by default.
I have updated the ReceiveMessageDirective to respect the messageAttributeName parameter and to no longer include attributes unless specified.