Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix message parse failed issue with AWS SQS #1448

Conversation

honkuan86
Copy link
Contributor

This PR is related to #1447 .

The changes is at SqsMessageCreator to default the HeaderResult.Success to true for all headers, so message can be parsed successfully when SNS message attributes are not present.

honkuan86 and others added 2 commits March 19, 2021 09:36
…e can be parsed successfully when SNS message attributes are not present.
@CLAassistant
Copy link

CLAassistant commented Mar 19, 2021

CLA assistant check
All committers have signed the CLA.

@iancooper
Copy link
Member

Thanks for this @honkuan86 . I'll skip worrying about the failing CI tests because it looks environmental. This change makes sense as it follows our tolerant reader mantra of trying to make it work even if you don't send us everything we need.

Can you sign the CLA? Then we are good to merge this

@honkuan86
Copy link
Contributor Author

Thanks for this @honkuan86 . I'll skip worrying about the failing CI tests because it looks environmental. This change makes sense as it follows our tolerant reader mantra of trying to make it work even if you don't send us everything we need.

Can you sign the CLA? Then we are good to merge this

Hi @iancooper , I have signed the CLA. Thanks.

@iancooper iancooper merged commit 837bc30 into BrighterCommand:master Mar 20, 2021
@holytshirt
Copy link
Member

@honkuan86 thank you for the PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AWS SQS - Unable to parse messages from non-Brighter services
4 participants