HTTP dataflow execution

The HTTP data plane stores registration state, dataflows and request logs. Its UI exposes runtime status and logs. Dataset authoring and consumer testing belong to applications such as Dataspace Starter.

The provider control plane selects a registered data plane by dataset ownership and its tsg:http-PULL profile. It prepares a dataflow with private backend configuration, then starts it to allocate a proxy address and authorization token. The consumer-pull side needs no local data plane.

Suspend, resume and terminate operations use the corresponding /dataflows/:id endpoints. Runtime completion and error notifications go to the tenant-scoped control-plane transfer callback API. API paths above are relative to the component's configured API base, including any subpath.

See configuration and dataset publication.