[Docs] AS Integrations AWS Lambda 2.0.0 Update #7329
Merged
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.
With the v2.0.0 release of
@as-integrations/aws-lambda
, the docs needed updates to reflect the new syntax and requirements. This PR also describes more of the added functionality in the 2.0 release.There was also an issue with the local event type that slipped through the cracks the first time around due to our runtime type-parsing. The local event we were using for testing was a
ProxyV1
event type, while thehttpApi
spun up byserverless
was of theProxyV2
type. I normalized the example event and integration example to both be the newV2
event type (as its now necessary to be explicit with v2.0.0).Fixes #7327 as
requestContext.http.method
was missing from the event as it was not required inProxyV1
, but is inProxyV2