The deactivate lifecycle fired BackendAccessRevokedEvent with actionDB's Unscoped session, so a listener's Delete through ev.Tx was a hard delete only for that reason. It now passes the save's transaction like every other site.
fireBackendAccessRevoked refuses a nil tx before any listener runs, and the Administrators and Roles update hooks fail closed (like the delete hook) when the save carries no transaction, instead of firing with whatever TxFromContext answered.
- cabana: BackendAccessRevokedEvent with reasons deleted, deactivated,
password_changed, password_set, password_reset and permissions, fired
synchronously inside the save's transaction; a listener error rolls back
- fired on admin delete, deactivate, a password set by another admin, an own
password change, admin:reset-password, a role/permissions/superuser change
and a role's permission change (every holder); MCPSubjectChanged unchanged
- role delete fires nothing (refused while the role has holders); no sign
out everywhere action exists
- smoke test TestBackendAccessRevokedSmoke (Postgres)