-
Notifications
You must be signed in to change notification settings - Fork 428
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.
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
Multitenancy for ejabberd users #3135
Conversation
This hook makes no sense without a host_type, it logically only triggers for a user that belongs to MongooseIM.
Codecov Report
@@ Coverage Diff @@
## master #3135 +/- ##
==========================================
+ Coverage 79.46% 79.49% +0.02%
==========================================
Files 395 395
Lines 32172 32170 -2
==========================================
+ Hits 25565 25572 +7
+ Misses 6607 6598 -9
Continue to review full report at Codecov.
|
dba715b
to
5a6b556
Compare
5a6b556
to
c51ebed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine for now, mongoose_users must be reimplemented with the proper caching solution once we pick one.
This erases
ejabberd_users
and creates a new module calledmongoose_users
that implements pretty much the same cache idea, but creates a table per host_type, and implements the remove_domain hook.It also chooses to extract the host_type from the accumulator in some places where we can be sure we do have a host_type, like, when run inside
user_send_packet
,filter_local_packet
, or iq handlers.