Add user activity table

Author: toddkazakov

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

@@ -27,11 +27,17 @@ spec:
     value.converter: 'org.apache.kafka.connect.json.JsonConverter'
     value.converter.schemas.enable: false
     snapshot.mode: {{ .Values.keycloak.snapshotMode }}
-    table.include.list: 'public.user_entity,public.user_role_mapping,public.keycloak_role'
+    table.include.list: 'public.user_entity,public.user_role_mapping,public.keycloak_role,public.tidepool_user_activity_event'
+    # Key the user-activity outbox by user_id (rather than the row's PK) so every
+    # event for a user lands on one partition and is consumed in commit order. This
+    # is what lets the clinic-worker consumer apply updates as last-writer-wins
+    # 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.type: 'io.debezium.transforms.Filter'
     transforms.filter.language: 'jsr223.groovy'
-    transforms.filter.topic.regex: '.+\.public.(user_entity|keycloak_role)'
+    transforms.filter.topic.regex: '.+\.public.(user_entity|keycloak_role|tidepool_user_activity_event)'
     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'))"
   tasksMax: 1
 {{- end }}