null scopes in ApiGatewayV2httpRequestContextAuthorizerJwtDescription

[mattrjacobs]

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:

• https://www.jeremydaly.com/verifying-self-signed-jwt-tokens-with-aws-http-apis/
• https://dev.to/martzcodes/token-authorizers-with-apigatewayv2-tricks-apigwv1-doesn-t-want-you-to-know-41jn

The aws-lambda-go repo defines this as Scopes []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.

[LegNeato]

@mattrjacobs we need to mark that as omitempty on the go side or we need to map null to the default on the rust side.

[mattrjacobs]

Thanks, I opened aws/aws-lambda-go#317

[mattrjacobs]

This has been fixed and merged on the Go side, and I confirmed that the diff on the generated Rust side looks as expected:

-    pub scopes: Vec<String>,
+    pub scopes: Option<Vec<String>>,

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!

[LegNeato]

Thanks for the bug report and the PR! Will cut a release with this soon 🍻