Dolph Mathews fe0c8e955b Do not prompt for scope options with default scoped tokens ... This changes the scope validation to occur after a token has already been created. Previous flow: 1. Validate authentication options. 2. Validate authorization options if the command requires a scope. 3. Create a token (using authentication + authorization options) 4. Run command. This means that scope was being checked, even if a default scope was applied in step 3 by Keystone. New flow: 1. Validate authentication options. 2. Create token (using authentication + authorization options) 3 Validate authorization options if the command requires a scope and the token is not scoped. 4. Run command. Change-Id: Idae368a11249f425b14b891fc68b4176e2b3e981 Closes-Bug: 1592062		2016-06-17 12:37:15 -04:00
..
api	Do not prompt for scope options with default scoped tokens	2016-06-17 12:37:15 -04:00
common	Do not prompt for scope options with default scoped tokens	2016-06-17 12:37:15 -04:00
compute	Merge "Move server image create command to its own resource file."	2016-06-16 13:05:18 +00:00
identity	Merge "Make set/unset command in identity and image pass normally when nothing specified"	2016-06-17 06:24:35 +00:00
image	Merge "Make set/unset command in identity and image pass normally when nothing specified"	2016-06-17 06:24:35 +00:00
locale	Imported Translations from Zanata	2016-06-04 06:18:46 +00:00
network	Support bulk deletion for delete commands in networkv2	2016-06-16 12:46:32 +00:00
object	osc-lib: command	2016-06-13 11:00:22 -05:00
tests	Do not prompt for scope options with default scoped tokens	2016-06-17 12:37:15 -04:00
volume	Merge "Standardize logger usage in volume"	2016-06-15 00:09:15 +00:00
__init__.py	Change version reporting to use pbr	2013-08-02 12:11:49 -05:00
i18n.py	Update translation setup	2016-01-29 08:18:50 +09:00
shell.py	Do not prompt for scope options with default scoped tokens	2016-06-17 12:37:15 -04:00