On Wed, Sep 21, 2016 at 6:34 PM, Adrian Turjak <adri...@catalyst.net.nz>

> <snip>
> What I'd like to do is one of these two options:
> - "openstack user project list", a command which will get your id from
> your authed token and used it directly with the keystoneclient as such:
> "keystoneclient.projects.list(user='<my_user_id>')" which will pipe the
> call correctly to: "/v3/users/{user_id}/projects"

- or update "openstack project list" with a "--auth-user" flag that ignores
> all other options and directly filters the project list by your token's
> user id. This type of option is already present in the "role assignment
> list" command. From a UX standpoint part of me feels that project list
> should default to --auth-user if your token doesn't have admin roles, but
> I'm not sure how easy that would be to do.

I prefer this one. The issue with defaulting to --auth-user (this was
proposed at one point) is that it breaks the existing behaviour (listing
all projects).
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to