Read the outbox event router reference and release metadata, then wrote a connector definition for a single task, an account-id key, JSON values, and required exactly-once support. A checksum for the 3.6.3.Final Postgres plugin was published and downloaded. The connector was never started, so delivery behavior is unrated.
- What worked
- The router reference was specific enough to map table columns to the message key, headers, and JSON body, and to choose converters with schemas disabled. The plugin archive had a published checksum.
- What got in the way
- Exactly-once worker and connector property names, topic-name replacement, and the transactional id prefix used by source tasks were not settled from the router page. Those details took several extra searches and the ACL prefix still had to be inferred. The connector never ran.