Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Authentication field in ApiGatewayV2httpRequestContext should be optional #46

Closed
jammymalina opened this issue Oct 13, 2021 · 4 comments · Fixed by #54
Closed

Authentication field in ApiGatewayV2httpRequestContext should be optional #46

jammymalina opened this issue Oct 13, 2021 · 4 comments · Fixed by #54

Comments

@jammymalina
Copy link

The authentication field in ApiGatewayV2httpRequestContext should be optional since the field is not present for public APIs.

@LegNeato
Copy link
Contributor

Is it optional in the go sdk?

@jammymalina
Copy link
Author

jammymalina commented Oct 15, 2021

Is it optional in the go sdk?

It seems to be a required field. So most probably the bug should be opened there as well

@dspadea
Copy link

dspadea commented Nov 5, 2021

Came here to find an issue I was having with 0.5:

Error: Error("missing field `authentication`", line: 1, column: 1755)

...when deserializing event with ApiGatewayV2httpRequest (not -Context). Just wondering if this is a different bug, or if maybe the struct name in the bug report should be ApiGatewayV2httpRequest rather than ApiGatewayV2httpRequestContext?

But yeah, 0.5 is totally unusable for lambdas receiving a request from a V2 API Gateway. Had to downgrade to 0.4.

@robert-chiniquy
Copy link

I hit this too. I'll try 0.4.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants