enable_catalog_ordered
Starts a server-side job that enables a catalog's taps level by level in their defined enable order, testing and running each tap before moving on. Returns a job id to track progress.
Instructions
Start one server-side job that enables a catalog's taps in their enable order (see catalog_enable_order): level by level, each tap is tested if it has no passing test, enabled, given one real run, and the job waits until that run's data has landed before moving on. A tap whose source did not land data is skipped with the reason; every tap's outcome is reported. Call this ONLY when the user has asked to enable the catalog's taps. It returns at once with the job id and the plan; follow progress with catalog_enable_order (its job block), pausing with wait_seconds between polls, until job.active is false, then report each tap's phase and reason. While the job runs, do not call run_tap, test_tap or update_tap on that catalog's taps: the job is already running them. Refused while another enable job for the catalog is running, or when its taps have a dependency cycle (the cycles are returned). Cancelling is done by the user in Datris. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.
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": {
"catalog": "<catalog>"
},
"name": "enable_catalog_ordered"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Optional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it. | |
| catalog | Yes | Catalog name. |