alawadi.cloudDocs
API Reference

Deploy API

Reference for the deploy request that rolls a new container image to an existing app.

Roll out an image

This is the project-scoped deploy you trigger while signed in with Google. For deploys driven from CI with a short-lived deploy token, use the Deployments API instead.

The deploy endpoint accepts a target container and image reference, validates ownership and registry policy, then records deployment status.

The image must already exist in your registry. Push it first via the GitHub OIDC deploy guide, or push directly to your private registry.

Pin image tags

Every deploy is an immutable OCI image. Reference a unique, immutable tag (for example the commit SHA), not :latest. The platform rejects :latest and untagged images with 400 BAD_IMAGE, so a redeploy always rolls the exact image you built.

POST
/v1/projects/{projectId}/containers/{containerId}/deploy

Authorization

bearerAuth
AuthorizationBearer <token>

Bearer JWT obtained after Google sign-in in the portal.

In: header

Path Parameters

projectId*string
containerId*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/containers/497f6eca-6276-4993-bfeb-53cbbbba6f08/deploy" \  -H "Content-Type: application/json" \  -d '{    "image": "registry.alawadi.cloud/acme/web:sha-8f31c2a"  }'
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "image": "string",
  "status": "queued",
  "created_at": "2019-08-24T14:15:22Z"
}
{
  "error": "validation failed",
  "request_id": "01J9Z3K8QWERTYUIOP"
}

On this page