-
Notifications
You must be signed in to change notification settings - Fork 350
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: looks like a typo - network interfaces with attached elb wont lo… #1251
fix: looks like a typo - network interfaces with attached elb wont lo… #1251
Conversation
…ad into neo4j because they are tuple instead of string
Hi, thanks for the PR, this does look like a typo (oops). I'm surprised the tests didn't catch this - can you please post the crash log? What version of neo4j are you using? |
Oh, maybe the tests didn't catch it because the tests don't have a case where there is attached ELB. 🤔 |
Thank you! |
neo4j version 4.4.3 Traceback (most recent call last): |
Fixes #1253 |
cartography-cncf#1251) When gathering network interfaces that have an attached ELB, neo4j ingestion fails due to this typo which turns the elbv1 variable into a tuple instead of a string.
When gathering network interfaces that have an attached ELB, neo4j ingestion fails due to this typo which turns the elbv1 variable into a tuple instead of a string.
reopening PR to fix CLA check