(apigateway): Add support for importing existing Cognito user pool authorizers
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 74
Description
Add support to import existing Cognito user pool authorizers, so I could use `aws_apigateway.Method` instead of `aws_apigateway.CfnMethod`.
### Use Case
I have multiple stacks using same API gateway. Base stack creates the authorizer and exports authorizer ID.
Other stacks should be able to use something like `apigateway.CognitoUserPoolsAuthorizer.from_authorizer_id(scope, 'Id', core.Fn.ImportValue('exported-authorizer-id'))`
### Proposed Solution
### Other
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
Contributor guide
Research direction
Start by locating the CognitoUserPoolsAuthorizer entry point and its existing authorizer construction APIs. Check how an authorizer ID could be supplied to support the from_authorizer_id usage described in the issue, then verify that an imported authorizer can be passed to aws_apigateway.Method instead of aws_apigateway.CfnMethod. Done means the cross-stack authorizer ID can be imported and used by Method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- api, authentication, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100