Kandji device

[chandanchowdhury]

Add support for Kandji device.

#1293

[chandanchowdhury]

@achantavy Requesting review of this PR

[achantavy]

Thank you for the PR! Appreciate you taking the time and effort to adopt cartography patterns used in other modules.

For this PR, let's focus on introducing a Kandji device node and a Kandji account/tenant node. Having a tenant-like node is needed for cartography automatic cleanup jobs to work so that the data in the graph is always up to date. You can copy this PR as a good example: https://github.com/lyft/cartography/pull/1083/files

Let's also defer adding the crowdstrike relationship and the analysis jobs to separate PRs.

Basically just copy that example PR and tag me again when this is ready. @ me on Slack if you need faster answers to fast questions; this way we can be better at the back and forth needed sometimes in these reviews.

Thanks again.

[achantavy]

Almost there, left a note about relationship direction convention. Once that is done, we can merge!

This is looking super clean btw

[achantavy]

Since the relationship label is called DEVICE, the convention is to point to the device. Like this:

(:KandjiTenant)-[:DEVICE]->(:KandjiDevice)

So you would do LinkDirection.INWARD.

[chandanchowdhury]

Apologies for the confusion Alex!
The correct relationship is

(:KandjiDevice)-[:ENROLLED_TO]->(:KandjiTenant)

I had updated the doc but forgot to update the comment (fixed now).

Does the relationship makes sense now?

[achantavy]

Thank you for your PR! Appreciate you taking the time to use the patterns and adjust

[chandanchowdhury]

Thank you @achantavy for reviewing the changes and walking me through the steps!