connect-declarative-schema

To import a custom service catalog and CMDB data, you shape source records as JSONL and map them into new graph nodes using declarative YAML schemas. This process joins business metadata like team ownership and application criticality with existing cloud and identity nodes.

Setting up declarative schema ingestion for AWS or GCS requires configuring S3 or GCS storage plumbing, authoring a YAML schema with mandatory identifiers and relationship joins, and shaping your source records as JSONL files for graph ingestion.

Yes, you can join CMDB records with existing cloud accounts and identity nodes. By defining relationship joins in your declarative YAML schema, the ingestion process connects your custom business context directly to current cloud and identity graph data.

You map JSONL source records into graph nodes by authoring a declarative YAML schema. This schema defines required identifier fields, node labels, properties, and relationship joins needed to accurately structure your custom business data within the graph.

Mandatory fields when authoring a YAML schema for graph ingestion include required identifiers, node labels, properties, and relationship joins. You must also specify your storage provider, bucket name, schema identifier, node types, and join fields.

Yes, declarative schema ingestion works with both AWS S3 and Google Cloud Storage. The workflow supports provider specific S3 or GCS plumbing to successfully sync your custom business data into the SubImage graph.