cinder/cinder/api
Sean McGinnis e918482674 Use constants for microversion values
We very often end up with merge conflicts for any patches that increment
microversions due to conflicting numbers. We can't really solve that,
but we can avoid the need to update version numbers throughout the code
by defining a constant value in one place and using that variable instead.

Change-Id: Ib3a80fee6caaabb49af097aa197f550c65d94985
2017-09-22 08:15:56 -05:00
..
contrib Use constants for microversion values 2017-09-22 08:15:56 -05:00
middleware Extracted HTTP response codes to constants 2017-03-22 12:00:41 +05:30
openstack Use constants for microversion values 2017-09-22 08:15:56 -05:00
v2 Use constants for microversion values 2017-09-22 08:15:56 -05:00
v3 Use constants for microversion values 2017-09-22 08:15:56 -05:00
views Use constants for microversion values 2017-09-22 08:15:56 -05:00
__init__.py Remove API v1 2017-09-06 07:39:10 -05:00
common.py Use constants for microversion values 2017-09-22 08:15:56 -05:00
extensions.py Remove log translations 2017-03-19 14:59:57 +00:00
microversions.py Use constants for microversion values 2017-09-22 08:15:56 -05:00
urlmap.py Remove unused logging import and LOG global var 2016-05-20 17:17:38 +08:00
versions.py Use constants for microversion values 2017-09-22 08:15:56 -05:00