Jamil 38c1de351c refactor(portal): move membership events to WAL (#9388) ...

Membership events are quite simple to move to the WAL:

- Only one topic is used to determine which client(s) receive updates
for which Actor(s).
- The unsubscribe was removed because it was unused.
- Notably, the N+1 query problem regarding re-evaluating all access
again after each membership is updated is still present. This will be
fixed using a lookup table in the client channel in the last PR to move
events to the WAL.

Related: https://github.com/firezone/firezone/issues/6294
Related: https://github.com/firezone/firezone/issues/8187

2025-06-06 06:23:33 +00:00

..

lib

refactor(portal): move membership events to WAL (#9388)

2025-06-06 06:23:33 +00:00

test

refactor(portal): move membership events to WAL (#9388)

2025-06-06 06:23:33 +00:00

.formatter.exs

feat(portal): Add REST API (#5579)

2024-07-20 04:20:43 +00:00

mix.exs

chore(portal): Bump LoggerJSON to 7.0.0, fixing config (#8759)

2025-04-11 19:00:06 -07:00