[dargmuesli]

Points the Debezium connector at vibetype_private.outbox only, instead of capturing vibetype.event, vibetype.upload and the notification table directly, and routes outbox events with the EventRouter SMT to vibetype.outbox.<aggregate_type> topics keyed by aggregate_id. The outbox deletes its rows right after inserting them, so the connector skips delete and truncate operations and emits no tombstones. Routed topics are created with a 7 day retention; topics that already exist keep theirs and need it set once. The outbox purge job and the Grafana notification queries are removed, since the table is always empty now.

Rollout: outbox rows written after the database migration but before the connector picks up this configuration are not captured, so both have to go out in the same deployment, at a quiet moment. The former vibetype.vibetype.event, vibetype.vibetype.upload and vibetype.vibetype_private.notification topics receive nothing afterwards and can be deleted.

Depends on maevsi/sqitch#325.

[dargmuesli]

Holding this for the major after v22. Once it stops capturing vibetype.event directly, reccoom no longer receives events: its consumer still subscribes to vibetype.vibetype.event by default (KAFKA_TOPIC in src/consumer/config.py) and reads Debezium's op field, which the EventRouter output on vibetype.outbox.<aggregate_type> does not carry. reccoom needs a matching change, or KAFKA_TOPIC set here, before this can merge.