We're initialising Library Bundle eligibility checks on user login, so as we deploy the big Proxy/Bundle code changes, we'll want a migration or somesuch that also drops all active sessions, forcing users to log back in.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Samwalton9-WMF | T240120 Launch Proxy and Library Bundle access methods | |||
| Resolved | jsn.sherman | T235262 Implement Library Bundle functionality | |||
| Resolved | jsn.sherman | T236287 Create a management command to email proxy/bundle users for the rollout | |||
| Resolved | jsn.sherman | T244895 Drop all sessions and email users when deploying Library Bundle |
Event Timeline
Comment Actions
We agreed it would make sense to have one 'proxy-launch' management command which was capable of both sending the announcement email and also dropping active sessions. The command should also clear out any existing 30-day edit count data to refresh the grace period.
Comment Actions
I did the session clearing as a migration, as we also talked about doing it that way?
Will add the 30 day edit count reset to the management command once I've rebased staging.
I could also certainly move the session clearing code there as well.