users: Increment app version for changes w.r.t. inactive users

- Since previous release 24.20 already has a increment to version 6, users app
version must be incremented in order for the changes related to inactive users
to take effect.

Tests:

- On applying the patches and running the service, upgrade to new app version
runs and succeeds. If there are inactive users presets, then before the setup()
privileged method is run, setup_and_sync_user_states() is run.

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
This commit is contained in:
Sunil Mohan Adapa 2024-09-24 14:28:25 -07:00
parent 761ee7d183
commit 373ca60f11
No known key found for this signature in database
GPG Key ID: 43EA1CFF0AA7C5F2

View File

@ -47,7 +47,7 @@ class UsersApp(app_module.App):
app_id = 'users'
_version = 6
_version = 7
can_be_disabled = False
@ -111,7 +111,7 @@ class UsersApp(app_module.App):
if not old_version:
privileged.first_setup()
if old_version and old_version < 6:
if old_version and old_version < 7:
# Setup password policy and lock LDAP passwords for inactive users.
inactivated_users = _get_inactivated_users()
if inactivated_users: