You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
I am working on switching the payload type from 1.0 to 2.0 for an HTTP API I'm working on. When I did that with a stock Cognito JWT authorizer, I started receiving "scopes": null from my API Gateway. The definition in this crate is scopes: Vec<String>, so that doesn't work.
This appears to be a common input from API Gateway -> Lambda, as seen in these examples:
There are other changes on the Go side as well, so I will let you decide when to do another sync, but this issue can now get closed once the sync is done. Thanks!
I am working on switching the payload type from
1.0
to2.0
for an HTTP API I'm working on. When I did that with a stock Cognito JWT authorizer, I started receiving"scopes": null
from my API Gateway. The definition in this crate isscopes: Vec<String>
, so that doesn't work.This appears to be a common input from API Gateway -> Lambda, as seen in these examples:
The
aws-lambda-go
repo defines this asScopes []string
json:"scopes"``.I don't know enough about Go and the codegen you're doing to know if the problem is in the initial Go data structure or in the codegen.
The text was updated successfully, but these errors were encountered: