Automatic handling of images that contain more components than API limit #152
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
This PR is my attempt to address the component limit inside of AWS Inspector API, without changing the AWS Inspector backend.
Currently, there is no standard way to handle images with over 5000 components.
My solution is to expand the
invoke_inspector_scanfunction.Changes include:
max_api_callswhich controls the maximum number of API calls to provide an upper limit on cost (default 1).Related Issues