cleandataengineering.aiData Platform, from the big picture to the code
You are here: Start here › Code map › Who calls what › governance

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

DefinitionWhat it does (its own first sentence)Called byNamed in tests
Action
class, line 22
_diff · governance/catalog.py:67
plan_sync · governance/catalog.py:92
test_semantic_governance.py, test_governance_catalog.py and 7 more
_table_tags
function, line 31
desired_entries · governance/catalog.py:50no test names it
desired_entries
function, line 46
catalog_actions · realms/databricks/semantic_governance/generate.py:129test_governance_catalog.py
_diff
function, line 64
plan_sync · governance/catalog.py:88no test names it
plan_sync
function, 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:129test_governance_catalog.py
apply
function, 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:20silver_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

DefinitionWhat it does (its own first sentence)Called byNamed in tests
Rule
class, line 22
rules_from · governance/coverage.py:38no test names it
Covered
class, line 30
coverage · governance/coverage.py:60no test names it
rules_from
function, line 36
Rules from the catalog's obligation files (each a YAML list).main · scripts/dac_coverage.py:33test_dac_coverage.py
_cited
function, line 42
coverage · governance/coverage.py:58no test names it
valid_waiver
function, line 47
coverage · governance/coverage.py:55test_dac_coverage.py
coverage
function, line 53
main · scripts/dac_coverage.py:40test_dac_coverage.py
summary
function, line 69
main · scripts/dac_coverage.py:41test_bundle.py, test_dac_coverage.py and 1 more
left
function, line 73
Rules with neither a test nor a waiver: MUST first, then by id.main · scripts/dac_coverage.py:47no 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

DefinitionWhat it does (its own first sentence)Called byNamed in tests
GovernanceError
class, line 38
A contract or manifest that cannot be turned into catalog entries.table_from_contract · governance/tables.py:129
dataset_key · governance/tables.py:166
test_governance_catalog.py
ColumnSpec
class, line 43
table_from_contract · governance/tables.py:140
module level · governance/tables.py:71 (value)
test_lakeformation.py, test_access_model.py
ColumnSpec.protected
method, line 50
none found in the codetest_lakeformation.py, test_access_model.py and 1 more
ColumnSpec.tokenised
method, line 54
plan_access · access/model.py:147 (value)test_semantic_governance.py, test_governance_catalog.py and 2 more
TableSpec
class, line 59
table_from_contract · governance/tables.py:146
table_from_view · governance/tables.py:183
test_lakeformation.py, test_access_model.py and 4 more
TableSpec.qualified
method, line 75
audit_sql · realms/databricks/semantic_governance/render.py:361 (by name)test_governance_catalog.py
product_of
function, line 82
consumers · governance/tables.py:92
table_from_view · governance/tables.py:172
no test names it
consumers
function, line 86
Dataset key ('<source>.<dataset>' for silver, 'gold.<name>' for gold) -> the products that read it.published_tables · governance/tables.py:205test_governance_catalog.py, test_dq_evaluator.py and 2 more
compute_tags
function, line 104
The tags every job and pipeline carries (cost_ledger kernel_owns, DPC-0062). Billing splits by these.none found in the codetest_governance_catalog.py
_owner
function, line 117
table_from_contract · governance/tables.py:143
owner_findings · governance/tables.py:217
no test names it
table_from_contract
function, line 123
published_tables · governance/tables.py:206test_governance_catalog.py
dataset_key
function, line 162
The key the manifest and the compute tags use for the dataset a contract describes.published_tables · governance/tables.py:206
table_from_contract · governance/tables.py:144 (value)
no test names it
table_from_view
function, line 171
generate · realms/databricks/semantic_governance/generate.py:163
published_tables · governance/tables.py:208
no test names it
published_tables
function, line 201
Every table and view the catalog must describe, sorted by layer, schema and name.build · realms/databricks/semantic_governance/generate.py:115test_governance_catalog.py
owner_findings
function, line 212
(contract, the manifest that pins it) pairs where the two name different owners (CAT-01: every difference is reported, never silently resolved). The catalog takes the contract's owner.build · realms/databricks/semantic_governance/generate.py:123test_governance_catalog.py