Bug 1041832

Summary:	[RFE][python-glanceclient]: Determine which commands a user can access and restrict the CLI
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/python-glanceclient/+spec/command-restraints
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_discussion
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:27:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:32:43 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/python-glanceclient/+spec/command-restraints.

Description:

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.

Specification URL (additional information):

None