Ken: if the query string is not provided, then it's a different call (list users). As for your question on the client side, I share your hesitation (and don't have an answer), but I think we've shot ourselves in the foot by making the <user-id> a positional argument, rather than keystone user-get [--id=<user-id>] [--name=<user-name>]. A fix will have to go into python-openstackclient as well; it's not too late for a more elegant solution there.
It looks like bug 1055763 duplicates this, although they're filed against separate projects. A patch is in review for keystone itself:
Patch: https:/ /review. openstack. org/#/c/ 14275/
Bug: https:/ /bugs.launchpad .net/keystone/ +bug/1055763
Ken: if the query string is not provided, then it's a different call (list users). As for your question on the client side, I share your hesitation (and don't have an answer), but I think we've shot ourselves in the foot by making the <user-id> a positional argument, rather than keystone user-get [--id=<user-id>] [--name= <user-name> ]. A fix will have to go into python- openstackclient as well; it's not too late for a more elegant solution there.