Create a new formation

POST 
/api/v1/formations

Validates the template, creates the formation record, then provisions all declared resources in dependency order.

A template-shape error is refused with 400. A deploy failure is not: the operation ran, so the formation is returned with 201 and status: "failed", and error explains why (the resources created before the failure are rolled back). Read status — a 2xx here means the deploy was attempted, not that it worked. The builtin CLI exits non-zero on that body so create-formation && … does not lie.

Request

Responses

201

Formation created

400

Bad Request

401

Unauthorized

403

Forbidden — either the caller may not operate on formations in the project, or it lacks an action a resource this template declares requires. error.meta.denied_actions names every missing action; nothing is applied.

409

Formation with this name already exists

413

REQUEST_REJECTED — the request body is over the size the body parser accepts

429

QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens

Response Headers

Retry-After

Seconds until the quota window admits a request again

500

Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded