Sean Dague d359196c32 parametrize max_api_version in tests ... There is a chunk of what turns out to be largely busy work in trying to land a microversion by adjusting a set of tests to always have the new max microversion. Many of these can be parametrized so that is not needed (and reduces some nearly irrelevant changes to every microversion patch). This doesn't reduce any test coverage. The api_samples static docs still need to get updated, so docs won't be missed. The intentionally created merge conflicts on rest_api_version_history.rst will ensure bumps are required. Change-Id: I0765b4a6b33fed77b210f72dcd281eb6aad8f564		2016-02-05 18:54:58 -05:00
..
v2-version-get-resp.json.tpl	update API samples to use endpoints	2015-12-10 08:32:41 -05:00
v21-version-get-resp.json.tpl	parametrize max_api_version in tests	2016-02-05 18:54:58 -05:00
versions-get-resp.json.tpl	parametrize max_api_version in tests	2016-02-05 18:54:58 -05:00