Adds OperationName to API Gateway Proxy Request #224
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
operationName is included by API Gateway for API's that were imported through OpenAPI spec.
jackrk
approved these changes
Aug 19, 2019
|
@jackrk I will rebase the change and update the pull request. |
bmoffatt
approved these changes
Aug 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
operationName is included by API Gateway for API's that were imported through OpenAPI spec.
Issue #, if available:
N/A
Description of changes:
API Gateway APIGatewayProxyRequestContext varies depending on the way how the API is being created. If I use
aws apigateway import-rest-apiSee. The model of the event used to call Lambda will contain additional attribute.One of such attributes is
operationNamethat will be populated from OpenAPI operationId attribute.This pull request adds this additional field to allow handling it on the Lambda side.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.