-
-
Notifications
You must be signed in to change notification settings - Fork 692
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
fix: permission for lambda-to-lambda async calls #141
fix: permission for lambda-to-lambda async calls #141
Conversation
@antonbabenko, no idea why this is failing the check but have a look when you can as the error seems like there is something wrong with the runner environment. |
Thanks for the fix! Looks good to me. @bryantbiggs Do you have an idea what can this be with GH Actions? |
@antonbabenko ya, I don't have a good solution for
something we need to think about how we want to support this, and how it fits into our static checks process |
I wonder what has changed recently so that we have this error (failed run):
https://github.com/antonbabenko/pre-commit-terraform/blob/master/terraform_docs.sh#L58 I am fine with running |
|
@bryantbiggs Thanks for the help! This one is passing fine now. Let's see when it break next time and we fix it better :) Merging this one. |
v1.45.0 has been just released. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
The async policy is missing the action to asynchronously call other lambda functions. Duplicate of #140, which I messed up somehow due to using github UI for the first time.
Description
Added lambda:InvokeFunction into the policy document for async integrations.
Check https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html as it states
"This operation requires permission for the lambda:InvokeFunction action."
Motivation and Context
When I deployed a lambda of which the destination_on_success is another lambda arn, my caller lambda failed to call my callee lambda due to a permission error.
Breaking Changes
Does not break backwards compatibility as it is an added permission.
How Has This Been Tested?
After adding the above changes on my local terraform module, the lambda integration works as expected, i.e. it has the permission to call another lambda asynchronously.