Mercurial > prosody-modules
view mod_groups_migration/mod_groups_migration.lua @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | dd3bfe8f182e |
children |
line wrap: on
line source
local host = module.host; local usermanager = require"core.usermanager"; local mod_groups = module:depends("groups_internal"); local default_group_id = module:get_option("group_default_id", "default"); local default_group_name = module:get_option("group_default_name", "default"); local function trigger_migration() if mod_groups.exists(default_group_id) then module:log("debug", "skipping migration, group exists already") return end module:log("info", "migrating to mod_groups!") local group_id = default_group_id; local ok, err = mod_groups.create({name=default_group_name}, true, group_id); if not ok then module:log("error", "failed to create group: %s", err) return end for user in usermanager.users(host) do mod_groups.add_member(group_id, user, true); module:log("debug", "added %s to %s", user, group_id) end module:log("debug", "synchronising group %s", group_id) mod_groups.sync(group_id) module:log("info", "added all users to group %s", group_id) end module:hook_global("server-started", trigger_migration, -100)