AGENT SKILL

pm-etl

Run bounded ETL syncs from configured connections.

License 许可
AGPL-3.0
所属仓库
polymetrics-ai/cli
最近更新
2026-09-21
Stars
★ 7
Forks
0

01 前言 Front Matter

name
pm-etl
description
Run bounded ETL syncs from configured connections.

03 SKILL.md 正文

pm-etl

  • Use pm etl run --connection <name> --stream <stream> --json.
  • Use --batch-size for large streams when the caller requests bounded memory behavior.
  • Supported sync modes are full_refresh_append, full_refresh_overwrite, full_refresh_overwrite_deduped, incremental_append, and incremental_append_deduped.
  • For the closed managed-PostgreSQL route, run pm etl transport postgres-managed-target plan --connection <name> --stream <stream>, preview the plan, then send its one-time token through pm etl run ... --approval-token-stdin --confirm destructive; PostgreSQL and declared API sources use sealed catalogs, and callers never supply raw SQL or target identifiers.
  • For a connector-declared typed destination, run pm etl transport declarative-typed-destination plan --connection <name> --stream <stream>, preview it, then use the ordinary approved ETL run. The saved stream's destination_action selects the connector-owned writes.json action; never accept it, a route, method, body, mapping, connector, or evidence as a run-time flag.
  • In pm etl run --json and pm etl status --json, inspect run.destination_results for each provider-successful typed action. A later local receipt or acknowledgement failure leaves the run uncheckpointed but retains ordered sanitized provider evidence. Concrete configured credential material is masked; provider-owned field names and ordinary values remain available.
  • A terminal run.status=delivered_reconciliation_required means the provider effect, read-back, and checkpoint are already durable. Preserve its exact ETLRun and categorized nonzero exit; rerun only the same saved connection and stream so pm repairs its declared delivery_reconciliation locally before endpoint resolution and never replays source or destination I/O. Never replace it with a normal retry or a raw provider action.
  • Incremental modes and deduped compatibility names require a cursor. Deduped modes require a primary key; static manifests advertise the full deduped compatibility name only with both fields and incremental modes only with a declared incremental executor. The deduped compatibility names refuse before source I/O until a matching transport is admitted.
  • Inspect batch_count and checkpoint in JSON output after runs.

04 同仓库更多 Skills