Create Deployment
Accept the deployment and queue the plan (202). Poll GET /deployments/{id}: plan_summary fills in when the plan succeeds; a failed plan leaves the record “failed” with the tofu output in its logs.
The viewer gate resolves the tenant with the 404-no-leak rule; creating the deployment then requires deployment.request at that tenant (s12 D2), so a read-only user sees the tenant but cannot deploy into it (named 403). ADR-0023: the create is account-bound, an operator on the connection’s account (additive levels: an account grant, or a raised tenant viewer) creates without a tenant-wide permission; a connection outside the caller’s visibility does not exist.
Parameters
Section titled “ Parameters ”Cookie Parameters
Section titled “Cookie Parameters ”Request Body required
Section titled “Request Body required ”Template selection plus tenant/connection scope. params validates against the blueprint registry’s per-template schema (app/blueprints.py). links (D6: a list, a pipeline needs two) validate against the compatibility matrix in the same accept.
object
One blueprint link created with the deployment (ruling R4). direction “feeds_into”: the NEW deployment is the source feeding the named existing deployment; “fed_by”: the named existing deployment feeds the new one.
object
object
Responses
Section titled “ Responses ”Successful Response
object
object
object
object
object
Validation Error