rename_catalog
Rename a catalog in one server-side operation, relabelling all associated taps and pipelines and moving the empty-catalog placeholder when explicitly requested.
Instructions
Rename a catalog: every tap and pipeline labelled with catalog is relabelled to new_name in one server-side operation, and the empty-catalog placeholder moves with it. Call this ONLY when the user has explicitly asked to rename that catalog — never to emulate a rename by calling set_catalog on each item. new_name must not already exist: a rename never merges catalogs and is refused if the target exists. To combine two catalogs, move their items with set_catalog. Uncataloged cannot be renamed, and new_name must use letters, digits, '_' and '-' only. Items that could not be moved come back under failed (the rest still move); report them to the user. API keys whose capabilities are scoped to the old catalog name are listed under affectedKeys — they keep the old scope and no longer match the renamed items, so tell the user an administrator may need to update those keys. 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>",
"new_name": "<new_name>"
},
"name": "rename_catalog"
}
}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 | Current catalog name. | |
| new_name | Yes | New catalog name (letters, digits, '_' and '-'). |