Enterprise Deployment Guide

Define ownership models and schemas for CSV assets to prevent drift and conflicts in multi-team setups.

Edit this page on GitHub

Shared Asset Governance

Assets (CSVs) are the ground truth of the graph. In a multi-team environment, it is critical to define who owns which assets to prevent configuration drift and conflicts.

Ownership Models

  • Centralized CMDB Export: A dedicated IT team maintains a central CMDB (like ServiceNow). A script periodically exports this data to CSV files and commits them to the Rescile Git repository.
  • Federated GitOps: Individual domain teams maintain their own CSV files within their team’s directory in the Git repository. A CODEOWNERS file enforces that the Networking team must approve changes to data/assets/subnets.csv, while App teams can freely edit data/assets/applications.csv.
  • Automated Discovery: Use Data Generators to automatically overwrite certain CSV files (like cloud compute instances) on every run, treating them as ephemeral caches rather than human-managed files.

Asset Schemas

Enterprise blueprints can define explicit column schemas in their module.toml for assets managed by other teams. This validates the structure before processing:

If a team commits an invalid value to their asset CSV, the pipeline will fail immediately, preventing malformed data from entering the graph.