Skip to content
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 NoneType error in describe_images by filtering out None values in… #1310

Merged
merged 3 commits into from
Jun 17, 2024

Conversation

austincomstockzoom
Copy link
Contributor

This merge request fixes an issue where the describe_images function in cartography/intel/aws/ec2/images.py encountered a NoneType error. The error occurred because None values were being included in the image_ids list, which is not allowed by the AWS SDK. In one particular account of several hundred tested, an image ID was returned that was None. I was able to verify that this allows all of my accounts to run ingestion successfully.

@achantavy
Copy link
Contributor

Thanks for the fix, looks good to me, should be good to merge after you sign the CLA

@austincomstockzoom
Copy link
Contributor Author

Check again, thanks

@achantavy achantavy enabled auto-merge (squash) June 17, 2024 21:16
@achantavy
Copy link
Contributor

Thank you!

@achantavy achantavy merged commit feece9d into lyft:master Jun 17, 2024
5 checks passed
chandanchowdhury pushed a commit to juju4/cartography that referenced this pull request Jun 26, 2024
lyft#1310)

This merge request fixes an issue where the `describe_images` function
in `cartography/intel/aws/ec2/images.py` encountered a NoneType error.
The error occurred because None values were being included in the
image_ids list, which is not allowed by the AWS SDK. In one particular
account of several hundred tested, an image ID was returned that was
None. I was able to verify that this allows all of my accounts to run
ingestion successfully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants