catalog_enable_order
Get the order to enable a catalog's taps by dependency level, showing which taps are ready, blocked, tested, or landed, so you run sources before dependents.
Instructions
Read-only. The order to enable a catalog's taps in: taps grouped into levels, level 1 first (taps that read no other tap's tables), then the taps that read tables produced by level 1, and so on. A tap's dependencies are its declared dependsOn or, when it declares none, the taps the platform inferred from the tables its script queries. Per tap: hasPassingTest (last test run succeeded on the tap's current script; a test of an older script does not count), lastRealRunLanded (last real run landed records), blockedBy (dependencies that have not landed data yet) and ready. A tap whose sources have not landed data fails its test, so run the sources first. Taps on a dependency cycle are listed under cycles. Use it to answer "what order do I enable these in", e.g. after restore_catalog, where every tap is disabled with no data landed.
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": "catalog_enable_order"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| catalog | Yes | Catalog name. |