lambda-proxy
lambda-proxy copied to clipboard
A simple AWS Lambda proxy to handle API Gateway request
Currently, any error in a route will get exposed to the caller: https://github.com/vincentsarago/lambda-proxy/blob/master/lambda_proxy/proxy.py#L697-L705: ```python try: response = route_entry.endpoint(**function_kwargs) except Exception as err: self.log.error(str(err)) response = ( "ERROR", "application/json", json.dumps({"errorMessage": str(err)}),...
When using the `$default` integration in an HTTP API, all requests result in a "Missing or invalid path" error. The code in the Lambda function: ``` from lambda_proxy.proxy import API...
Environment details: + OS: macOS + Python version: python3.7/3.8 + lambda-proxy version: 5.2.1 Issue: We are trying to apply lambda-proxy for our AWS Lambda Development. However there is some problem...
I am passing in users names in a first.last format and using a GET method to query information out of a table. When I pass in a username that does...
Resolves #49 I would like to know your opinion about the attempt before continue work. I'm aware of some commented code and missing tests regarding new payload version.
This PR is a first sketch for next lambda-proxy version (6) Changes: - New way to create and handle response - New way to hander exception - FastAPI/Starlette style API...
If >= 4 items are returned from `route_entry.endpoint`, the fourth is assumed to be a `dict` with override parameters for the HTTP response. This is then combined with the default...
If `custom_headers` is supplied, it adds arbitrary key-value pairs from the `dict` to the response message object. Using a `dict` for `custom_headers` is ideal, because it essentially removes the need...
Finally found the doc describing the new http event. With the new http API aws also introduced a new payload version: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
replace #27