Chelabase
ManagementFunctions

List a function's deployments

GET
/v1/databases/{id}/branches/{branch_id}/functions/{name}/deployments

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Database id

Formatuuid
branch_id*string

Branch id

Formatuuid
name*string

Function name

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/branches/497f6eca-6276-4993-bfeb-53cbbbba6f08/functions/string/deployments"
[  {    "bundle_sha256": "string",    "bundle_size": 0,    "compatibility_date": "2019-08-24",    "created_at": "2019-08-24T14:15:22Z",    "created_by": "string",    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "note": "string",    "rollout": "pending",    "spec": {}  }]

Create a function, or change its kind or its auth on the branch PUT

Creates the function when the database has none of this name (201), else changes what the body names (200). A name is a lowercase letter, then up to 62 of a-z, 0-9 and `-`; `public` is reserved (the keyless invoke prefix). Changing the kind needs Admin and is refused while a protected branch has the function active.

Deploy a bundle, or a service's spec POST

A function: stores the manifest (byte for byte as sent, at most 10 MiB; the body at most 12 MiB) with the functions service. A service: checks the `spec`'s URL (a tenant admin only). Then records the deployment and, unless `activate` is false, makes it the active one on the branch. The function's enabled state doesn't change.