-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat(apigatewayv2): add role support for lambda authorizers #35706
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
base: main
Are you sure you want to change the base?
feat(apigatewayv2): add role support for lambda authorizers #35706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This review is outdated)
328e4b9 to
e44073f
Compare
e44073f to
2e73226
Compare
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
|
@pahud, any chance to get this looked at? It's been a while. |
I can confirm this PR has been in the pr/pending-community-review queue. With re:Invent just around the corner, the team's bandwidth is limited, so there may be some delay before they can review. In the meantime, please ensure your PR maintains passing CI checks. |
Issue # (if applicable)
Closes #35696.
Reason for this change
Added support for specifying the role to use to invoke an authorizer.
Description of changes
Added an optional
role: iam.IRoleto relevant interfaces and passing it down to the L1 construct.Description of how you validated changes
Added unit tests and updated the integration test.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license