Matthew Treinish fc7cd8f577 Only use accounts.yaml with locking provider ... This commit removes support for using an accounts.yaml file with the non-locking provider. There is no reason the non-locking provider would ever need to be used with an accounts.yaml file because the locking provider supports running serially just fine. (which would be the sole use case for accounts file with the non-locking provider) Doing this relegates the non-locking provider to just handle the legacy config options for providing credentials. Removing this code path provides the advantage of removing a double maintenance burden for the non-locking provider, in addition to simplifying the config and user story around the cred providers. It also turns out this config permutation was never properly tested and didn't actually work. Change-Id: I8088d75897589203264ae29326fe9901c3457cc3		2015-03-30 13:18:22 -04:00
..
field_guide	Remove Whitebox tests	2013-09-12 15:40:15 +00:00
HACKING.rst	Tempest Coding Guide	2013-06-09 22:02:19 +02:00
REVIEWING.rst	Add REVIEWING.rst	2014-08-21 20:54:10 -04:00
cleanup.rst	Add tempest post-run cleanup script	2014-09-19 01:58:58 -04:00
conf.py	Stop using intersphinx	2014-09-25 10:06:42 +02:00
configuration.rst	Only use accounts.yaml with locking provider	2015-03-30 13:18:22 -04:00
index.rst	Add tempest config guide doc	2015-02-24 11:24:18 -05:00
javelin.rst	Adds documentation for Javelin	2014-12-18 20:06:48 +02:00
overview.rst	initial seed for tempest doc directory	2013-05-22 21:06:55 -04:00