Flags

All four flags work on every command (validate, run, version), though --dry-run is only meaningful on run.

--verbose

Print extra detail. On validate, that's the parsed pipeline structure (module list, defaults inheritance, env-var positions). On run, it's per-record trace lines as records move through the filter chain.

cannectors run --verbose pipeline.yaml

Output:

· loading pipeline sync-orders v1.0.0
· defaults: timeoutMs=15000, onError=log, retry.maxAttempts=2
· input  httpPolling   GET https://source.example.com/api/orders
· record 1/48 → mapping (kept)
· record 1/48 → condition (status==paid: kept)
· …
✓ complete  47 records · 1.84s

Useful when you need to know why the runtime made a particular decision. Don't ship --verbose to production logs — it's noisy.

--quiet

Suppress informational logs. Warnings and errors still print.

cannectors validate --quiet pipeline.yaml && echo "ok"

The exit code is still set correctly, so this is the right flag for CI gating: silence on success, errors on failure.

--log-file <path>

Write logs to a file instead of stdout. The file gets the same structured records that would have been printed; stdout stays clean.

cannectors run --log-file /var/log/cannectors/sync-orders.log pipeline.yaml

The log format is line-delimited JSON (one event per line). Pipe it into your log aggregator (Loki, Datadog, etc.) without further parsing.

--dry-run

run-only. Validates, fetches the input, runs every filter, then prints what would have been sent to the output instead of sending it.

cannectors run --dry-run pipeline.yaml

See Dry-run mode for the full semantics.

Combining flags

Flags compose freely:

cannectors run --dry-run --verbose --log-file run.log pipeline.yaml

The order doesn't matter. The pipeline file argument can come anywhere (Cobra-style flag parsing).

See also