Skip to content

Conversation

@sercasti
Copy link

@sercasti sercasti commented Oct 4, 2023

  1. I updated the Lambda implementation to use an “Integration Proxy” style interface by adding as a dependency the “aws-lambda-java-events” sdk and using the “APIGatewayV2HTTPEvent” artifact in the lambda interfaces
  2. Now the lambda receives the full request event and returns the full response event, which includes the content-type definition, the CORS headers, and the response status code.
  3. The lambda now uses Amazon powertools-serialization library to bind the incoming body on the request to the internal DTO object for the add and remove endpoints.
  4. The lambda parses the incoming Path Parameter “uuid” for the “getUnicornsBasket” from the request event. (event.getPathParameters().get("uuid"))
  5. Moved the Lambda to the next version 0.0.2 as these changes are not backwards compatible

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

scastine added 5 commits October 3, 2023 16:08
…hich means, full request and response objects with status code, cors headers, content type and path parameters values within the Lamda implementation, using the Lambda events SDK
…ck from previous lambda version, as it is not backwards compatible
…library, instead of having 2 redundant ones, making the code cleaner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant