Andrey Avtomonov 9ac37166f5 fix(connections): enforce scan_enabled:false on explicit scan/ingest commands ... scan_enabled:false promised the connection is 'never used as a scan/ingest target,' but the predicate only gated automatic selection — explicit ktx scan <id> / ktx ingest <id> still resolved the connection id and reached the live-database introspection path, so an execute-only connection could still be scanned or ingested. Guard runKtxScan and runKtxIngest at entry: if the target connection is execute-only, refuse with an actionable error (remove the flag to scan, or use ktx sql to query) before doing any work. This makes the flag a single declaration honored on every scan/ingest entry point, not just auto-selection.		2026-06-09 14:28:05 +02:00
..
docs	fix(connections): enforce scan_enabled:false on explicit scan/ingest commands	2026-06-09 14:28:05 +02:00