-
-
Notifications
You must be signed in to change notification settings - Fork 45
feat: add optional source_account to lambda permissions #87
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?
Conversation
- Make both source_arn and source_account optional in invoke_function_permissions - Add comprehensive documentation for all permission fields - Update complete example to demonstrate source_account usage - Maintain backward compatibility with existing configurations 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
|
/terratest |
oycyc
left a comment
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.
Good addition! As defined on the AWS provider docs as well: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lambda_permission#source_account-1
|
Ugh seems like Terratest is failing because of the optional... @rorynolan in your branch, can you try setting the examples/versions and where the required_version of TF to be >= 1.3.0 or >=1.4.0? |
Head branch was pushed to by a user without write access
|
@oycyc I set it to minimum 1.4 can you please trigger a test rerun? |
|
/terratest |
what
why
Without this, you need to add custom stuff just to comply with the config rule lambda-function-public-access-prohibited, that requires
source_accountto be set.It should be easy to comply with this rule using the module natively.