-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat: add payloadformatversion to httpapi events #1517
feat: add payloadformatversion to httpapi events #1517
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.
For future reference- I think we'll have to add this field to Globals somehow, since if we get additional versions ("2.1", "3.0", "4.0", etc), it would be nice if they could all be configured in one property.
@@ -210,7 +210,7 @@ def add_lambda_integration( | |||
path_dict[method][self._X_APIGW_INTEGRATION] = { | |||
"type": "aws_proxy", | |||
"httpMethod": "POST", | |||
"payloadFormatVersion": "1.0", | |||
"payloadFormatVersion": "2.0", |
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.
Does this mean we default to 2.0 payloadFormatVersion in SAM?
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.
Ahh.. yes, as stated in the docs below.
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.
Yes, the default value is "2.0" in SAM
Issue #, if available:
Description of changes:
Description of how you validated changes:
Checklist:
make pr
passesexamples/2016-10-31
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.