You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for filling out a bug report, we really appreciate any help in improving the CloudGraph CLI and providers!
Describe the bug
In the process of executing CG_DEBUG=5 cg scan aws, there is some error messages such as "unable to store data in Dgraph". These are from "alb, apiGatewayRestAPI, cloudwatchEventRule, kinesisFirehose, s3, securityHubStandardSubscription, vpc" services.
I check "Your data for aws has been saved to /root/.local/share/cloudgraph/cg/version-9" messages, for example in "kinesisFirehose" service there is 2 resources in "cg/version-9/aws_1697656492879", but unable to store this data in Dgraph. Understand? Help me.
To Reproduce
Steps to reproduce the behavior:
cg init
cg launch
CG_DEBUG=5 cg scan aws
and error
Please include the cg-debug.log file if applicable
Please solve this problem. Please able to store the data inDgraph.
@JohnDevel, I got a same problem.
At first time, My partner and I thought there would be any mismatched schema name.
But It wasn't. Please let me share experiment scenario.
as result of CG_DEBUG=5 cg scan
As you see, getting data is ok.
I tried to insert data gathered into dgraph, as defined mutation. mutation($input: [AddawsVpcInput!]!) { addawsVpc(input: $input, upsert: true) { numUids } }
It worked well as shown below snapshot.
Activity
JohnDevel commentedon Oct 23, 2023
Please solve this problem!!!
novad03 commentedon Nov 2, 2023
@JohnDevel, I got a same problem.
At first time, My partner and I thought there would be any mismatched schema name.
But It wasn't. Please let me share experiment scenario.
as result of

CG_DEBUG=5 cg scanAs you see, getting data is ok.
I tried to insert data gathered into dgraph, as defined mutation.

mutation($input: [AddawsVpcInput!]!) { addawsVpc(input: $input, upsert: true) { numUids } }It worked well as shown below snapshot.
I hope it would be very helpful to you.
I will Keep tracing on this bug.
Sincerely,
Thank you.
tyler-dunkel commentedon Nov 8, 2023
Please check if the steps here help resolve your issue. Unfortunately it is an issue internal to Dgraph that they have not fixed yet. #117 (comment)