Skip to main content

SetProjectGatewayWorkspace

POST 
/admin/v1/project-gateways/:id/workspace

Reassign a project gateway to a different dataplane (workspace).

A data plane serves ONLY the hostnames of project gateways whose workspace_id matches its own (via per-gateway host-scoped routes plus the P10 authz map). Moving a gateway is therefore NOT a bare DB flip: this RPC tears down the gateway's per-gateway routes + authz binding on the OLD data plane and materializes them on the NEW one, refreshing both workspaces' authz maps and default-route suppression.

The gateway's hostname is unchanged, so DNS is NOT moved automatically: the hostname still resolves to the OLD data plane's ingress until an operator repoints it. Until that cutover, requests to the hostname hit the old data plane (now torn down) and 404. The response ALWAYS includes a warnings entry reminding the operator to repoint DNS (and provision the new data plane's TLS cert). Recommended order: provision the new data plane's DNS/cert, call this RPC, then cut DNS over.

Reassigning to the gateway's current workspace is a no-op. The new workspace must exist for the gateway's customer, and the gateway's slug must be free in the new workspace (a collision is rejected with ALREADY_EXISTS).

Request​

Responses​

Success