Closed Bug 1104783 Opened 10 years ago Closed 10 years ago

deleting all permissions does not remove a user from the permissions page

Categories

(Release Engineering Graveyard :: Applications: Balrog (frontend), defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: peterbe)

References

Details

I noticed this while playing around on aus4-admin-dev - if I delete all of the permissions a user has, they continue to appear in the list of users after the modal dialog disappears. Totally minor thing.
So, so I send something like a "DELETE /api/users/:userid" if the number of permissions is reduced down to 0? Or should it be an explicit action? E.g.:

<button ng-show="!permissions.length" ng-click="deleteUser(user)">No permission, eh? Delete user</button>
I think you just need to remove the username from the list if their last permission is deleted. There's no reference to a user in Balrog except in the permissions table, which has a PK of (username, permission) - so when the last permission is deleted, the user is gone from the db.
This was fixed in the balrog-ui repo with this: https://github.com/mozilla/balrog-ui/commit/4b5d799614729405735d98f21ab27507a950e834

Now we just need to put this into balrog.
I'm hoping to do a push after we ship Firefox 34 next week to pick up this and any other pending changes.
Depends on: 1106159
Depends on: 1108573
Depends on: 1109115
In production.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Commits pushed to master at https://github.com/mozilla/balrog

https://github.com/mozilla/balrog/commit/5608f80fe8be21fef4feb525a2b47c9bcd9eb185
[balrog-ui] fixes bug 1104783 - last permission should remove user

https://github.com/mozilla/balrog/commit/b6722e1ef6e9cbeb17e0051588a63a2133b0301e
[balrog-ui] Merge pull request #3 from peterbe/bug-1104783-last-permission-should-remove-user

Bug 1104783 last permission should remove user
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.