Actions
Cleanup #36375
closedmgr/dashboard: Async unique username validation
Status:
Resolved
Priority:
Low
Assignee:
Category:
Component - Users & Roles
Target version:
% Done:
0%
Tags:
low-hanging-fruit
Backport:
octopus
Reviewed:
Affected Versions:
Pull request ID:
Description
If I try to create one user that already exists, the error message will only be displayed after pressing the submit button.
We should implement the same behavior that we have on Roles, where the error message is displays after the role name is filled.
Check out the RGW user form how it is implemented there:
https://github.com/ceph/ceph/blob/master/src/pybind/mgr/dashboard/frontend/src/app/ceph/rgw/rgw-user-form/rgw-user-form.component.ts#L57
https://github.com/ceph/ceph/blob/master/src/pybind/mgr/dashboard/frontend/src/app/shared/api/rgw-user.service.ts#L130
Updated by Volker Theile over 5 years ago
- Subject changed from Async unique username validation to mgr/dashboard: Async unique username validation
Updated by Nizamudeen A about 4 years ago
- Status changed from New to In Progress
- Assignee set to Nizamudeen A
Updated by Nizamudeen A about 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 34587
Updated by Lenz Grimmer almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
Updated by Nizamudeen A almost 4 years ago
- Copied to Backport #45346: octopus: mgr/dashboard: Async unique username validation added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 150 to Component - Users & Roles
Actions