Data PlatformZoom level 3
Who calls what: governance
Every class, function and method in the governance package, with who calls it. Found by reading the code. A call written as object.method() is matched by the method's name, so a same-named method elsewhere can appear: those rows say by name.
34 definitions in 4 modules. Jump to a module: catalog.py · coverage.py · port.py · tables.py
governance/catalog.py
Catalog entries filled from the contracts and the manifest (DPC-0075; SERV-01, SEC-01, CAT-01). Semantic layer
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
Actionclass, line 22 | _diff · governance/catalog.py:67plan_sync · governance/catalog.py:92 | test_semantic_governance.py, test_governance_catalog.py and 7 more | |
_table_tagsfunction, line 31 | desired_entries · governance/catalog.py:50 | no test names it | |
desired_entriesfunction, line 46 | catalog_actions · realms/databricks/semantic_governance/generate.py:129 | test_governance_catalog.py | |
_difffunction, line 64 | plan_sync · governance/catalog.py:88 | no test names it | |
plan_syncfunction, line 79 | Actions that make the catalog match the metadata, in a stable order (tables before their columns). Objects the metadata does not declare lose only our tags (a dropped contract must not leave its owner tag behind). | catalog_actions · realms/databricks/semantic_governance/generate.py:129 | test_governance_catalog.py |
applyfunction, line 96 | What the catalog holds after the actions run: the realm's statements must have exactly this effect. Used by tests and by the memory adapter; also lets a plan be checked to converge (apply then plan is empty). | MemoryCatalogState.apply · adapters/memory_catalog.py:20 | silver_helpers.py, test_baseline_stage.py and 15 more |
governance/coverage.py
DAC coverage (B20 C20): every platform rule has a passing test or a written waiver. Pure. Semantic layer
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
Ruleclass, line 22 | rules_from · governance/coverage.py:38 | no test names it | |
Coveredclass, line 30 | coverage · governance/coverage.py:60 | no test names it | |
rules_fromfunction, line 36 | Rules from the catalog's obligation files (each a YAML list). | main · scripts/dac_coverage.py:33 | test_dac_coverage.py |
_citedfunction, line 42 | coverage · governance/coverage.py:58 | no test names it | |
valid_waiverfunction, line 47 | coverage · governance/coverage.py:55 | test_dac_coverage.py | |
coveragefunction, line 53 | main · scripts/dac_coverage.py:40 | test_dac_coverage.py | |
summaryfunction, line 69 | main · scripts/dac_coverage.py:41 | test_bundle.py, test_dac_coverage.py and 1 more | |
leftfunction, line 73 | Rules with neither a test nor a waiver: MUST first, then by id. | main · scripts/dac_coverage.py:47 | no test names it |
governance/port.py
The catalog-state port (dpc/ports.yaml data_catalog): what the catalog holds now, so the sync plan can diff it. Semantic layer
governance/tables.py
Published tables, data products and the tag standard. Semantic layer