Skip to content

feat: migrate to Data Plane Signaling v1.0 (wire model, router, storage) - #22

Merged
paullatzelsperger merged 1 commit into
mainfrom
feat/signaling-v1-wire-model
Nov 9, 2026
Merged

paullatzelsperger merged 1 commit into
mainfrom
feat/signaling-v1-wire-model

Conversation

@paullatzelsperger

Copy link
Copy Markdown
Contributor

Breaking change: brings the SDK to Data Plane Signaling v1.0 (spec a0752cd, equal to v1.0-RC4). Phases 1 to 4 of the migration plan.

  • Wire model: v1.0 field names (messageId, dataFlowId, ...), profile/claims/labels/metadata replace callbackAddress/transferType, string state enum, DSP-shaped DataAddress, per-signal message types, DataFlowStatusMessage.
  • Core: push/pull derived from the profile suffix with the spec's dataAddress rules, /resume with same-party enforcement, COMPLETED is final, 409 on a duplicate /start, WithResumeProcessor and WithCompleteProcessor.
  • HTTP: NewHandler mounts all 8 routes under /v1 (stdlib ServeMux), correct Location headers, /started always returns a status body, /status returns DataFlowStatusResponseMessage.
  • Storage: Postgres schema rewritten for the new fields; memory store updated.
  • Tests: conformance tests against the published JSON schemas; integration tests rewritten against the router. Examples updated; chi removed.

Out of scope here: control plane callbacks, registration, authorization (next PRs).

🤖 Generated with Claude Code

Rewrite the wire model, SDK core, HTTP layer and storage for the Data
Plane Signaling specification v1.0 (a0752cd, v1.0-RC4). No backwards
compatibility.

- messages: spec JSON casing (messageId, dataFlowId, ...), profile and
  claims replace callbackAddress and transferType, labels and metadata,
  per-signal messages with required messageId, DataFlowStatusMessage,
  DataFlowStatusResponseMessage and ErrorResponse
- model: DSP DataAddress, DataFlowState serialized as the spec string
  enum, push/pull derived from the profile suffix, SuspendedBy, resume
  transition, COMPLETED is final
- SDK: processors return DataFlowStatusMessage, Resume and Started,
  data address rules for push and pull, duplicate /start is a conflict,
  WithResumeProcessor and WithCompleteProcessor
- HTTP: NewHandler mounts all 8 data plane routes under /v1 using
  net/http ServeMux patterns; chi is removed
- storage: new Postgres columns (profile, claims, labels, metadata,
  control_plane_id, suspended_by), memory store deep copies
- tests: JSON schema conformance tests against the published schemas,
  router and integration tests rewritten
- examples updated to the new API

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@paullatzelsperger paullatzelsperger self-assigned this Nov 9, 2026
@jimmarino
jimmarino self-requested a review November 9, 2026 13:23
@paullatzelsperger paullatzelsperger added the enhancement New feature or request label Nov 9, 2026
@paullatzelsperger
paullatzelsperger merged commit 5fec68a into main Nov 9, 2026
5 checks passed
@paullatzelsperger
paullatzelsperger deleted the feat/signaling-v1-wire-model branch November 9, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants