Fix #1320: Do not print an error when analysing a lambda function and its associated execution role was previously deleted. #1368
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
Currently, when analysing a lambda function but its associated role execution does not exist, ScoutSuite triggers a
NoSuchEntityException
exception, printing an error line.The current change set a condition to check this use case and not printing the corresponding error.
Fixes #1320
Type of change
Checklist: