Cleanup #36375
mgr/dashboard: Async unique username validation
Status:
Resolved
Priority:
Low
Assignee:
Category:
dashboard/usermgmt
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
Related issues
History
#1 Updated by Ricardo Marques about 2 years ago
- Assignee deleted (
Ricardo Marques)
#2 Updated by Ricardo Marques about 2 years ago
- Tags set to low-hanging-fruit
#3 Updated by Ricardo Marques about 2 years ago
- Priority changed from Normal to Low
#4 Updated by Volker Theile about 2 years ago
- Subject changed from Async unique username validation to mgr/dashboard: Async unique username validation
#5 Updated by Volker Theile about 2 years ago
- Description updated (diff)
#6 Updated by Nizamudeen A 10 months ago
- Status changed from New to In Progress
- Assignee set to Nizamudeen A
#7 Updated by Nizamudeen A 10 months ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 34587
#8 Updated by Volker Theile 9 months ago
- Backport set to octopus
#9 Updated by Lenz Grimmer 9 months ago
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
#10 Updated by Nizamudeen A 9 months ago
- Copied to Backport #45346: octopus: mgr/dashboard: Async unique username validation added
#11 Updated by Nathan Cutler 7 months 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".