-
Notifications
You must be signed in to change notification settings - Fork 400
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(parser): raise ValidationError when SNS->SQS keys are intentionally missing #1299
fix(parser): raise ValidationError when SNS->SQS keys are intentionally missing #1299
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
Codecov Report
@@ Coverage Diff @@
## develop #1299 +/- ##
========================================
Coverage 99.88% 99.88%
========================================
Files 119 119
Lines 5427 5427
Branches 619 619
========================================
Hits 5421 5421
Misses 2 2
Partials 4 4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, a minor suggestion to make the tests more explicit. Super excited to see your first PR ;-)
Co-authored-by: Heitor Lessa <[email protected]>
@heitorlessa thank you for the feedback, it makes 100% sense! 😎 |
Thanks a lot @rubenfonseca ;) |
Issue number: #1009
Summary
Changes
When
UnsubscribeURL
orSigningCertURL
were intentionally missing from the SNS -> SQS payload,KeyError
was thrown.Since the objective of the parser is to validate the payload, we changed the code so it returns
an expected ValidationError instead.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.