Skip to content

Add user activity to keycloak connector #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
toddkazakov wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Add user activity to keycloak connector #360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
44e4619
Remove summaries from updated fields in patient CDC events
toddkazakov May 11, 2026
fd5eec3
Add user activity table
toddkazakov Jun 10, 2026
5ed0ff2
Add user activity events
toddkazakov Jun 10, 2026
d9adfc5
Drop user-activity tombstones in connector filter
toddkazakov Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions charts/tidepool/charts/clinic/templates/5-patients-source-kafka-connector.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@ spec:
collection: patients
connection.uri: {{ .Values.global.kafka.connect.mongoConnectionUri }}
copy.existing: false
pipeline: '[ {$project: {"fullDocument.summary": 0}} ]'
startup.mode.copy.existing.pipeline: '[ {$project: {"fullDocument.summary": 0}} ]'
pipeline: '[ {$project: {"fullDocument.summary": 0, "updateDescription.updatedFields.summary": 0}} ]'
startup.mode.copy.existing.pipeline: '[ {$project: {"fullDocument.summary": 0, "updateDescription.updatedFields.summary": 0}} ]'
database: clinic
key.converter: org.apache.kafka.connect.json.JsonConverter
key.converter.schemas.enable: false
Expand Down
23 changes: 21 additions & 2 deletions charts/tidepool/charts/kafka/templates/2-users-source-kafka-connector.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,31 @@ 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,public.user_attribute'
transforms: 'filter,filter_user_attr'
table.include.list: 'public.user_entity,public.user_role_mapping,public.keycloak_role,public.user_attribute,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,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)'
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'
# Drop pruning-delete tombstones (null value) for this topic instead of the
# default 'keep', so they don't reach the consumer. Scoped to this filter's
# topic.regex, so the keycloak tables' tombstones are unaffected.
transforms.user_activity_filter.null.handling.mode: 'drop'
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)'
Expand Down