-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Allow Imported Lambda to create Permission #1709
Comments
If these two stacks are defined in the CDK app, you actually don't need to use I am closing for now, please let us know if this works for you. |
If I don't import the lambda in the api stack and just append it to the route itself, I get a Cyclic Dependency error. I will fiddle around a bit more tonight to see if I can get it working. |
Copy: @rix0rrr I think we have another one of those cyclic deps use cases. Any systemic way we can identify these you think? |
When I get home from the office tonight I'll create a repo with this error. |
I am seeing the exact same issue here. |
Stumbled to this same issue still. Two stacks, one for lambdas, the other for API Gateway. Creates a cyclic dependency:
|
I currently have 2 stacks. One for my Lambda's and the second for my API Gateway routes. When I import the lambda into my API Gateway stack and append it to a route, it creates the link between the Lambda and API but it doesn't add the appropriate permissions to invoke the lambda.
I was able to get around this by opening the aws-lambda module and changing the ImportedFunction property canCreatePermissions to true.
What is the main reason this isn't set to true and/or why can we not set this ourselves?
I think to organize stacks more appropriately aka a stack for Lambda's and a stack for routes, this would need to be set to true.
The text was updated successfully, but these errors were encountered: