add-node-type

To define a new node type in Cartography, you create and wire a CartographyNodeSchema into your existing module, specifying the node label, required properties, and sub-resource relationships to extend the graph data model.

Modeling a sub-resource relationship in Cartography involves attaching a sub_resource_relationship to a tenant-like node such as AWSAccount, AzureSubscription, or GCPProject within the new node schema definition.

Yes, Cartography node schemas support extra_node_labels, conditional labels, and scoped_cleanup settings, allowing you to tailor the ontology and enforce default cleanup behaviors for the new resource type.

The best way to extend a Cartography module with one-to-many transforms is to define a new CartographyNodeSchema that enforces standardized dataclass annotations and configures related edges to align with the module's ontology.

Yes, adding a new Cartography node schema requires an existing module to attach the schema to, enabling end-to-end module extension or new module scaffolding for the additional resource type.

Standardized dataclass annotations are required for Cartography node schemas to enforce correct relationship wiring, validate required properties, and ensure default behaviors for cleanup and transforms function properly.