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
Prior to this change, APIGatewayEvent.requestContext object available in custom authorizer lambda had accountId and apiId fields. We used these fields construct methodArn inside our authorizer lambda. But the above change deleted these fields. Any reason why the fields are removed? AWS Lambda @types still refer to these fields.
The text was updated successfully, but these errors were encountered:
thank you for filing the issue @newtechfellas I'm not able to see any accountId and apiId related changes in the PR you are referring to. could you create a small repro repository which outlines your issue? Labeling as a bug in the meanwhile.
@dnalborczykthis line and this line updated in the referenced pr overrides requestContext object of the event set here. As result we lost accountId and apiId fields in the requestContext parameter inside Lambda function.
Prior to this change,
APIGatewayEvent.requestContext
object available in custom authorizer lambda hadaccountId
andapiId
fields. We used these fields construct methodArn inside our authorizer lambda. But the above change deleted these fields. Any reason why the fields are removed? AWS Lambda @types still refer to these fields.The text was updated successfully, but these errors were encountered: