Ramon Petgrave

I realize the new schema is not discoverable from https://lyft.github.io/cartography/usage/schema.html I'll have to fix that and find a way to draft these documentation updates.

> +1 to this. Unfortunately, we're unable to use Cartography with any non-EOL'd version of Neo4j now :/. Is there anything we can do to help move this along? Hey,...

This effort is being tracked in #914

Also feel free to comment here.

> Hey, do we need this merged in? Can you share an invocation example and scenario of when you would want to use this? Added here. https://github.com/lyft/cartography/pull/866/files#diff-f46377f43949b669f9290eab5ffaacd38270a3b873ab60df84850deeb9c5931fR18-R25

From @ryan-lane https://github.com/lyft/cartography/pull/826#issuecomment-1109419468 > Could we separate out the analysis jobs that are intended to run along with > the code, from the ones that are intended to connect nodes...

You can try to alter the retry mode in your aws config file. Let us know if that helps. We may want to build this into cartography. https://boto3.amazonaws.com/v1/documentation/api/latest/guide/retries.html

@El070422 I missed that in your original post. Can you try to adaptive mode? Mainly because of it's client-side rate limiting.

Hey! Thanks for opening this. Yeah I agree it's tricky to know about this option, among others. We could probably add a few of the more common options here, I...

Thanks for the find. The preferred way is to not set the node property, instead of supplying an empty string. So, you may open a PR to simply not set...