De-scope users.reset_password_token index to be per-organization
What does this MR do and why?
De-scope users.reset_password_token index to be per-organization
Due to the constraints of the Cells architecture, we can no longer have globally UNIQUE indexes across all cells. Therefor we must scope unique indexes to the sharding constraint.
This change modifies the users.reset_password_token unique index put in place by Devise to be per-organization. In combination with the organization routing in the unlock instructions email, users should be routed to the correct cell where their unlock token can be looked up.
References
- See Epic for related MRs in-progress and rollout plan: &20097
- Issue: #562092
- MR updating email routes: !212116 (merged)
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #562092
Edited by Andrew Evans