Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Authorizer Lambda Request context missing accountId and apiId fields #1635

Closed
newtechfellas opened this issue Dec 23, 2022 · 2 comments · Fixed by #1640
Closed

Custom Authorizer Lambda Request context missing accountId and apiId fields #1635

newtechfellas opened this issue Dec 23, 2022 · 2 comments · Fixed by #1640
Labels

Comments

@newtechfellas
Copy link

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.

@dnalborczyk
Copy link
Collaborator

dnalborczyk commented Dec 27, 2022

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.

@newtechfellas
Copy link
Author

@dnalborczyk this 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants