-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DDO-3890] Add models.User.DeactivatedAt #683
Conversation
What's Changed
|
Quality Gate passedIssues Measures |
Adds a currently read-only field to represent a models.User being deactivated. This PR adds the field and other related logic that reads it:
This PR also allows super admins to modify the user records of other users through the API. Users could previously only edit themselves and super admins had to go through the database. This is in preparation for the deactivation field being mutable via a super-admin-only procedure endpoint.
Note that propagation is unaffected here. That whole system is unaware of a user being deactivated and it's only concerned with role assignment state. That's why it's important that we delete role assignments for deactivated users.
Testing
Tests for each feature updated to add coverage. Sherlock's strategy of testing the API JSON-to-JSON means that we've got high existing coverage protecting against regressions.
Risk
Low, and this one's an easy one to roll back which is some of why I'm splitting this out.