qqeasonchen opened a new pull request, #5396: URL: https://github.com/apache/eventmesh/pull/5396
## What Adds a complete connector documentation set under `docs/feature/connectors/`: one overview (model, running, catalog, matrix) plus one page per plugin for all 23 shipped connectors. Follow-up to #5394 (the 16 incomplete connector implementations fix) — now every plugin also has operator-facing docs, replacing the master-era website `03-connect` docs (which only covered 9 plugins) with full coverage of the new-architecture contract. ## Structure - `docs/feature/connectors/README.md` — the connector model (Source/Sink contract table from `eventmesh-connector-api`), at-least-once semantics, running a worker (`bin/start-connector.sh` + `CONNECTOR_OPTS`), common flags (`connector.offset.mode`, numbered `-Dconnector.N.*` form, `/admin/connectors` dynamic scheduling), plugin catalog grouped by category, and a 23-row plugin matrix (source/sink support + client dependency). - `docs/feature/connectors/<plugin>.md` × 23 — per plugin: Classes table (source/sink implementation classes + behavior summary), Source/Sink configuration tables (key / default / description, defaults taken from the actual `props.getProperty` calls in each connector), and a runnable example (`bin/start-connector.sh` with the plugin's `CONNECTOR_OPTS`). - `docs/feature/connectors/_category_.json` — sidebar position. - `docs/index.md` — adds a Connectors bullet to the Core features section. ## Plugins covered Message queues: kafka, rocketmq (4.x), rabbitmq, pulsar, pravega · Databases & storage: mongodb, redis, canal, jdbc, s3, file · Cloud & runtime: knative, openfunction, spring, http, prometheus · Chat & SaaS: dingtalk, lark, slack, wechat, wecom · AI: chatgpt, mcp ## Notes - Config tables were derived from the real `getProperty` defaults in each connector source, so the documented values match the code (including the 16 connectors completed in #5394). - Docs-only change; no code touched. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
