-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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 to return data when using lambda_info module #64548
Conversation
cc @pjodouin |
@stefanhorning, just so you are aware we have a dedicated Working Group for aws. |
I will also add some integration tests in a few minutes to catch regressions in the future. |
The test
The test
|
Looks like the integration test still misses AWS permission |
@stefanhorning Thanks for adding tests! Here are the policies we actually deploy for CI https://github.com/mattclay/aws-terminator/tree/master/aws/policy. Those were made open to the public after the hacking/ policies were already used by contributors for their own development, so they diverged (and the permissions we use in CI also need to be more strict). You can open a PR to that repo with the permissions that are missing. @jillr Has been reviewing/deploying those on Thursdays. |
Ok will look into it, once back from vacation. |
Added missing CI AWS permissions here mattclay/aws-terminator#78 Once deployed the tests should probably run through. |
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.
Thanks for this patch and the test cases @stefanhorning. We'll need some additional permissions to run these tests in the CI account though. Would you mind opening a PR in https://github.com/mattclay/aws-terminator? I think lambda:GetFunctionConfiguration, lambda:ListVersionsByFunction, lambda:ListAliases, lambda:ListEventSourceMappings
should cover it.
Co-Authored-By: Jill R <4121322+jillr@users.noreply.github.com>
@jillr I had already a PR open in aws-terminator mattclay/aws-terminator#78 which I used now to add the additional Also made the sanity-test related changes here as requested. |
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.
Tests look good, policy changes have been deployed. One request inline though.
… easier test setup.
@jillr PR is ready to be merged now. |
Thanks @stefanhorning and @jillr! |
* Clean up residual code from ansible#64548 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
* Clean up residual code from #64548 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
* Fixed issue 64479 with lambda_info module * Added integration tests for lambda_info module * Moved lambda_info tests into already existing aws_lamda testsuite for easier test setup. Co-authored-by: Jill R <4121322+jillr@users.noreply.github.com>
* Clean up residual code from ansible#64548 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
SUMMARY
Fix issue #64479 with lambda_info module.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
Jus opened this PR with the fix suggested by @s-hertel in the ticket #64479 .