GovOPlaN/govoplan-connectors
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: expose connector datasource origins

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-28 12:43:26 +02:00
parent ba5ccea5b0
commit 27302f0c39
7 changed files with 272 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@@ -15,13 +15,18 @@ or reporting behavior.
## Executable First Slice
The first executable connector capability provides tenant-isolated tabular
sources for Dataflow. Operators can import bounded JSON or CSV snapshots,
inspect inferred schemas, and expose immutable source references and content
fingerprints through `connectors.tabular_sources@0.1.0`.
origins. Operators can import bounded JSON or CSV snapshots, inspect inferred
schemas, and expose immutable source references and content fingerprints
through `connectors.datasource_origins@0.1.0`.
Database, API, file, and warehouse providers can implement the same core
capability later. Dataflow stores opaque references and expected fingerprints;
it never stores connector credentials.
Connectors owns acquisition, connection profiles, credentials, discovery, and
provider health. `govoplan-datasources` registers an origin as a governed live
or cached datasource and owns staging, materializations, frozen states, and
consumer access. Dataflow consumes that Datasources contract and never imports
connector implementations or stores connector credentials.
Database, REST/HTTP, directory, managed-file, and warehouse providers can
implement the same origin contract without changing Datasources or Dataflow.
Development: