usermanager.Client.UserInfo needs to be bulk-capable rather than all-or-nothing

[Roger Peppe]

Although the apiserver implementation returns an individual error for each user
specified in the UserInfo call, usermanager.Client.UserInfo concatenates all the returned
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.

[Anastasia (anastasia-macmood)]

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.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.