update_tap
Modify an existing tap's configuration without regenerating its script: enable or disable it, set a CRON schedule, change the target pipeline, or edit the description.
Instructions
Update an existing tap's CONFIG without regenerating the script. Change the enabled state, CRON schedule, target pipeline, or description. USE THIS to set or adjust a tap's schedule (cron_expression) whenever the user describes a recurrence (nightly, daily, every morning, market open, etc.). The platform's scheduler runs the tap on the cadence you set — no external cron, Airflow DAG, or shell loop is needed (or wanted). See the SCHEDULING RULE in the server instructions. VALIDATION RULE: if you're enabling a cron_expression on a tap whose script has NEVER been validated, call test_tap FIRST and confirm it succeeds. The cadence-change path is safe for taps that have already run successfully; it is not safe to set a cron on a never-tested script. The platform enforces this: setting cron_expression on an untested script returns HTTP 409 with the remedy — save the tap without the cron, call test_tap until it succeeds, then call update_tap again with the cron. Cadence-only changes on a tap whose current script has passed test_tap are accepted. To change the SCRIPT itself, call create_tap again with the same name and the new script or instruction — create_tap upserts by name and replaces the existing script. There is no separate script-only update tool. 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": {
"name": "<name>"
},
"name": "update_tap"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the tap to update | |
| reason | No | Optional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it. | |
| source | No | Declared source identity for lineage/provenance (provider name or host). Pass an empty string to clear it and fall back to derivation. | |
| enabled | No | Enable or disable the tap | |
| depends_on | No | Names of other taps in the same catalog whose destination tables this tap reads. Replaces the declared list; pass an empty list to declare that it has none (overrides the platform's inference from the script). Omit to leave it unchanged. Orders and explains catalog_enable_order only; never enforced. | |
| description | No | New plain-English description | |
| endpoint_url | No | For HTTP taps only: new endpoint URL Datris POSTs the run context to. Rejected on Python taps. | |
| cron_expression | No | Quartz CRON expression for recurring runs: 6 fields — seconds minutes hours day-of-month month day-of-week, plus an optional year (e.g., '0 0 * * * ?' for hourly, '0 30 5 ? * MON-FRI' for weekdays 5:30am). A 5-field Unix cron such as '*/1 * * * *' is NOT a Datris schedule: the save is refused with HTTP 400 whose `error` quotes the 6-field equivalent to resend. SET THIS whenever the user describes a recurrence — nightly, daily, hourly, market open, etc. The platform's scheduler fires the tap on this cadence automatically; do not propose external schedulers or shell cron for the user to run themselves. | |
| target_pipeline | No | New target pipeline name |