feat: Add httpEvent.operationId
to the request context
#1325
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.
Description
AWS ApiGateway defines a
operationId
value for each http event. This value is available in the running Lambda in theevent.requestContext.operationName
property. This property value is very helpful if validating requests against an OpenApi spec.This PR takes the
operationId
value and makes it available in theevent
model for bothLambdaProxyIntegrationEvent
andLambdaProxyIntegrationEventV2
Motivation and Context
This supplies a value that is available when running the Serverless deployment in the AWS environment, but until now, not available in the offline environment.
How Has This Been Tested?
I have added unit and integration tests. We have also been using this code internally for the past year.
Screenshots (if appropriate):