Determine which commands a user can access and restrict the CLI

Registered by Joshua Harlow on 2012-11-03

An idea. The glance cli provides a bunch of commands for user and admin usage when it seems like it could almost query keystone to see who the calling user is and restrict commands that are available (in help, and such) based on the information that keystone presents as 'possible' to be called in the first place. This would avoid confusion as to why admin commands are shown for users who could not call them in the first place anyway.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Yahoo Openstackers!
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.