Backend Deploy
backend_deployDeploy a Supabase backend from a spec after backend_render: migrations, secrets, auth, legal build, edge functions. Dry-run returns plan; live requires human approval.
Instructions
Deploy the spec's Supabase backend: migrations, secrets, auth, legal build and edge functions (live unless dry_run; needs human approval).
Use when: after backend_render. dry_run=true (default) returns the plan without any call. Not for: single SQL (supabase_run_sql) or one secret (supabase_set_secret). Returns: {ok, plan/steps, dry_run} or an approval_required refusal.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"app_dir": "<app_dir>",
"project_ref": "<project_ref>"
},
"name": "backend_deploy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app_dir | Yes | Absolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp. | |
| dry_run | No | If true (default) nothing is changed or sent and the exact plan/command is returned; false performs the live action. | |
| approval_id | No | Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id. | |
| project_ref | Yes | Supabase project ref to deploy to. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||