DR Runbooks

Execute Runbook

Create a dr_runs row, seed dr_run_steps from the YAML, enqueue the job.

The tenant_id is the Supabase auth user.id (uuid as string). All DB writes use the user's uuid for RLS tenant isolation.

post/runbooks/execute

Request

  • Base URL: https://api.continueops.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.continueops.com/runbooks/execute
  • Auth: API key in header X-Runner-Key

Request body

tenant_idstring required

Tenant (= Supabase auth user.id) as UUID string

credential_idstring uuid required

Which stored cloud credential to use

runbook_namestring required

Display name / slug of the runbook

runbook_pathstring nullable

Supabase Storage path to a user-supplied runbook YAML. Mutually exclusive with runbook_builtin.

runbook_builtinstring nullable

Slug of a baked-in runbook (e.g. 's3-route53-failover' or 'aws/s3-route53-failover'). Mutually exclusive with runbook_path.

variablesobject

Resolved runbook variables

execute_on'continueops' | 'agent'

Which executor runs the job. 'continueops' (default) enqueues to the CPLN-hosted cont-dr-runner via Redis. 'agent' skips Redis and leaves the dr_runs row pending so an enrolled in-VPC dr-agent picks it up via /agent/v1/jobs/poll.

Response

Successful Response

run_idstring uuid required
status'pending' | 'running' | 'completed' | 'failed' | 'cancelled'
started_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.