[Feature] Publish module outputs as immutable datasource materializations #3

Open
opened 2026-07-28 12:48:19 +02:00 by zemion · 1 comment
Owner

Parent: #1

Define a producer-side lifecycle contract so Dataflow and other modules can
publish outputs without importing Datasources internals.

Acceptance criteria:

  • versioned stage/publish DTO and capability for module-owned producers
  • idempotency key and producer/run/revision provenance
  • bounded inline output plus durable artifact/object reference support
  • atomic publication of materialization metadata and current-state change
  • configurable frozen/publication label
  • audit event and notification-ready terminal state
  • Dataflow publishes a pinned run output and returns a datasource/materialization reference
  • Workflow can wait for publication success, warning, review-required, or failure
Parent: https://git.add-ideas.de/GovOPlaN/govoplan-datasources/issues/1 Define a producer-side lifecycle contract so Dataflow and other modules can publish outputs without importing Datasources internals. Acceptance criteria: - versioned stage/publish DTO and capability for module-owned producers - idempotency key and producer/run/revision provenance - bounded inline output plus durable artifact/object reference support - atomic publication of materialization metadata and current-state change - configurable frozen/publication label - audit event and notification-ready terminal state - Dataflow publishes a pinned run output and returns a datasource/materialization reference - Workflow can wait for publication success, warning, review-required, or failure
Author
Owner

Codex State: progress

Summary

  • Implemented the versioned datasources.publication capability and SQL provider in 8ae7dac; Core contract is baa2143.
  • Producer module/run provenance, idempotent replay and conflict detection, immutable materializations, optional frozen labels, existing/new targets, and returned datasource/materialization references are covered.

Verification

  • Datasource tests: 10 passed.
  • Connector -> Datasources -> pinned Dataflow publication composition passed in govoplan 5b79e7d.

Next / Blocked

  • Keep open for durable artifact/object references, high-concurrency idempotency/revision hardening, generic audit/notification emission, and Workflow terminal-state consumption.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented the versioned datasources.publication capability and SQL provider in 8ae7dac; Core contract is baa2143. - Producer module/run provenance, idempotent replay and conflict detection, immutable materializations, optional frozen labels, existing/new targets, and returned datasource/materialization references are covered. ### Verification - `Datasource tests: 10 passed.` - `Connector -> Datasources -> pinned Dataflow publication composition passed in govoplan 5b79e7d.` ### Next / Blocked - Keep open for durable artifact/object references, high-concurrency idempotency/revision hardening, generic audit/notification emission, and Workflow terminal-state consumption. Suggested status label: `status/in-progress`
zemion added
status
in-progress
and removed
status
ready
labels 2026-07-28 13:51:38 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-datasources#3
No description provided.