usermanager.Client.UserInfo needs to be bulk-capable rather than all-or-nothing
Bug #1561526 reported by
Roger Peppe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Although the apiserver implementation returns an individual error for each user
specified in the UserInfo call, usermanager.
errors into a string, losing error type info, so
a) there's no way to make a UserInfo call on a single user and find out whether that
user exists or not.
b) there's no way to get information for a bunch of users at once without failing
all-or-nothing.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: 2.0-count juju-release-support |
affects: | juju-core → juju |
To post a comment you must log in.
Since this report was originally filed, usermanager. Client. UserInfo has been adjusted to take in a list of users as a filter. So you can do (a).
However, indeed, the call is not very tolerant when a result contains information for several users some with errors, creating all-or-nothing scenario.
I'll rename the bug.