Update lambda-manager code to handle ThrottlingException [CDS-1331] #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… have more then 50 lo groups, and rewite most of the python code
royfur
reviewed
Jul 1, 2024
…subscription to log group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
- Add config to boto3 in order for the lambda to not fail in case of ThrottlingException error from AWS.
- Update the python code so it will not thought errors in case the lambda cant add subscription to log group.
- In case the user will update the cloudformation after its creation then the SCAN_OLD_LOGGROUPS will be set to true again, added another function and condition to handle it ->
Fixes #update_scan_all_log_groups_statusHow Has This Been Tested?
Checklist: