Add user activity events

Author: toddkazakov

charts/tidepool/charts/kafka/templates/2-users-source-kafka-connector.yaml

@@ -34,11 +34,20 @@ spec:
     # safely; combined with snapshot.mode=never it removes out-of-order/replay
     # regressions. Other tables keep their default primary-key based message key.
     message.key.columns: 'public.tidepool_user_activity_event:user_id'
-    transforms: 'filter'
+    transforms: 'filter,user_activity_filter,filter_user_attr'
     transforms.filter.type: 'io.debezium.transforms.Filter'
     transforms.filter.language: 'jsr223.groovy'
-    transforms.filter.topic.regex: '.+\.public.(user_entity|keycloak_role|tidepool_user_activity_event)'
+    transforms.filter.topic.regex: '.+\.public.(user_entity|keycloak_role)'
     transforms.filter.condition: "value.op && (((value.op == 'r' || value.op == 'c' || value.op == 'u') && (value.after && value.after.realm_id && value.after.realm_id == '{{ $realm }}')) || (value.op == 'd'))"
+    # Realm filter scoped to the user-activity outbox only. Keeps inserts (and any
+    # snapshot reads/updates) for the configured realm and drops everything else,
+    # including pruning deletes (their `after` is null, so they fail the check) —
+    # the clinic-worker consumer ignores deletes anyway. Records on other topics do
+    # not match this regex and pass through untouched.
+    transforms.user_activity_filter.type: 'io.debezium.transforms.Filter'
+    transforms.user_activity_filter.language: 'jsr223.groovy'
+    transforms.user_activity_filter.topic.regex: '.+\.public.tidepool_user_activity_event'
+    transforms.user_activity_filter.condition: "value.op && (value.op == 'r' || value.op == 'c' || value.op == 'u') && value.after && value.after.realm_id && value.after.realm_id == '{{ $realm }}'"
     transforms.filter_user_attr.type: 'io.debezium.transforms.Filter'
     transforms.filter_user_attr.language: 'jsr223.groovy'
     transforms.filter_user_attr.topic.regex: '.+\.public.(user_attribute)'