-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Validate SNS developer endpoints #11621
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
Conversation
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.
LGTM ✔️ Thanks for expanding the test coverage!
@@ -514,8 +588,6 @@ paths: | |||
- $ref: '#/components/parameters/SnsPhoneNumber' | |||
responses: | |||
'204': | |||
content: | |||
text/plain: {} |
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.
Q: is this because the body is empty? If so, is there another way to state the response mimetype?
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.
Yep, it is because the body is empty. Afaik, omitting the response type is the way to go in these cases.
Motivation
After introducing OpenAPI specs for our internal endpoints, we are now introducing stricter validations in our test pipeline.
This PR enables the validation of the requests and responses for the developer endpoints in the SNS test suite.
It also adds minor changes to the specs to reflect the actual implementation and make the suite green.
Changes