Closed HVKukkonen closed 4 months ago
Could you add a test to cover this case?
Added. Of course, nothing guarantees that the fixture used exactly matches the event from the API Gateway but that's the same issue with all of the fixtures, right? :smiling_face_with_tear:
Could you fix the linting errors?
Issue #, if available: None
Description of changes: Fixes typing issue with
ApiGatewayV2CustomAuthorizerV2Request
not allowing forNone
as theidentity_source
. I suspect this being an issue as per the docsAlso, I have run into issues with this in the wild as not having the identity source in the API Gateway Terraform configuration results in
DeserializeError { inner: Error { path: Path { segments: [Map { key: \"identitySource\" }] }, original: Error(\"invalid type: null, expected a sequence\"
in my Authorizer code. And after specifying an arbitrary field from the API Gateway event as the identity source it worked fine.By submitting this pull request