Chelabase
ManagementFunctions

List a function's schedules on the branch

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

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/schedules"
[  {    "cron": "string",    "enabled": true,    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "next_run_at": "2019-08-24T14:15:22Z",    "timezone": "string"  }]

A container service's last 200 log lines on the branch GET

Stdout and stderr of the container that runs the service's active deployment on the branch. Container services only; needs Developer (logs can hold what a service prints).

Add a schedule to a function on the branch POST

At each due time the function's `scheduled(controller, env, ctx)` handler runs once, with `controller.cron` and `controller.scheduledTime`, while the function is enabled on the branch. A cron has 5 fields (minute granularity); ticks missed while the worker was down run once. A new branch inherits the schedules.