Implement Lambda response transformation to API Gateway format #1927
+462
−1
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
gcbeattyAWS
changed the title
normj
approved these changes
Jan 14, 2025
philasmar
approved these changes
Jan 15, 2025
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.
Issue #, if available: DOTNET-7861
Description of changes:
This PR introduces functionality to transform AWS Lambda InvokeResponse objects into API Gateway compatible response formats. The implementation adds support for REST API, HTTP API v1, and HTTP API v2 response formats.
This change is needed because API gateway has additional conversion logic in some cases when converting lambda memory stream to the api gateway response object, as described in https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
This change does not implement handing the LambdaResponse.FunctionError case, for when the lambda itself failed. I think that should be handled separately.
I have ran all unit tests and integration tests locally and it passed
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.