Connector coverage & requests (tracking)

Conduit's connector strategy isn't to hand-build a catalog issue-by-issue — it's to make connectors **easy to build in any language** (Go, Python, Rust, TypeScript via the SDKs), **distribute them through the registry**, and offer a **Kafka Connect wrapper** for instant catalog parity. So we're consolidating the open connector *requests* into this single tracking issue rather than keeping dozens of separate tickets that imply a central build queue.

### Want a connector?
- **Upvote it** here (👍 on this issue, and mention which one in a comment).
- **Better — build it.** `conduit connector new --lang ` scaffolds a working connector repo (SDK wiring, tests, CI, release workflow) in minutes, and the registry gets it distributed. See the connector SDK docs.

### How we prioritize official connectors
By demand signal (this list + reactions) and the roadmap. Per [ROADMAP.md](https://github.com/ConduitIO/conduit/blob/main/ROADMAP.md), the near-term official connector focus is: a best-in-class **Apache Iceberg** destination, production-grade **CDC sources** (Postgres, MySQL, MongoDB, SQL Server, Oracle), and the **AI-pipeline** sinks (pgvector, Qdrant, Pinecone), plus warehouses (Snowflake, ClickHouse, BigQuery).

### Requested so far
- #410 — Connector: Amazon SNS [Source]
- #892 — Google Analytics Source Connector
- #989 — Cassandra source connector
- #1063 — Connector: File Diff
- #1073 — Connector: AWS Kinesis Source
- #1111 — Connector: Memphis.dev Source/Destination
- #1163 — Connector: Informatica Source
- #1164 — Connector: Informatica Destination
- #1565 — Connector: Spanner [Source/Destination]
- #1566 — Connector: AlloyDB [Source/Destination]
- #1567 — Connector: CloudWatch Logs [Source]
- #1568 — Connector: CloudWatch Metrics [Destination]
- #1570 — Connector: Azure Cognitive Search [Destination]
- #1571 — Connector: Azure Data Lake Storage Gen2 [Destination]
- #1572 — Connector: Azure Event Hubs [Source/Destination]
- #1573 — Connector: Azure Functions [Destination]
- #1574 — Connector: Azure Log Analytics [Destination]
- #1575 — Connector: Azure Service Bus [Source]
- #1576 — Connector: Azure Synapse Analytics [Destination]
- #1577 — Connector: Datadog Metrics [Destination]
- #1579 — Connector: GitHub [Source]
- #1580 — Connector: Google Cloud Big Table [Destination]
- #1581 — Connector: Google Cloud Dataproc [Destination]
- #1582 — Connector: Google Cloud Functions [Destination]
- #1584 — Connector: Jira [Source]
- #1585 — Connector: MQTT [Source/Destination]
- #1586 — Connector: OpenSearch [Destination]
- #1587 — Connector: PagerDuty [Destination]
- #1588 — Connector: ServiceNow [Source/Destination]
- #1590 — Connector: Splunk [Destination]
- #1594 — Connector: Surrealdb [Source/Destination]
- #1995 — Connector: Amazon Aurora DSQL [Destination]
- #2000 — Connector: directory connector [Source/Destination]
- #2003 — Connector: Clickhouse [Destination]
- #2004 — Connector: Typesense [Destination]
- #2005 — Connector: Meilisearch [Destination]
- #2006 — Connector: SQLite [Source/Destination]
- #2007 — Connector: Manticoresearch [Destination]
- #2219 — Connector: Box [Source/Destination]

---

Closing the individual issues in favor of this consolidated list isn't a "no" — it's how we track connector demand honestly. If you filed one of these, it's captured here; add a 👍 and a comment to signal priority, or pick it up with the scaffolding above.

This is a tracking issue rather than a scoped code change. Start with the connector SDK docs and ROADMAP.md, then use the listed requests and the `conduit connector new --lang ` entry point to choose a concrete connector. Done is not defined for the tracking issue itself.

Written by the indexing model from the issue text.