I once built a terraform provider for a custom neo4j cmdb to be able to add metadata in the form of additional relationships to anything provisioned with TF.
This data was used for config inventory, job scheduling and a bunch of other automations/rules.
Broke the ”cloud vendor” boundry this way and we used it seamlessly against on-prem vsphere and aws.
Never got around to open source it, unfortunately.
A graph for this type of cmdb/config data is really useful.
Thanks for the comment! Cartography can definitely be extended to do multi-cloud but we're focusing on AWS at the moment. At the same time though we didn't want to discourage others from looking at this by saying in the docs that it was solely an AWS project. There's nothing really stopping it from supporting other data sources.
Edit: we're planning on adding a GitHub module soon too.