
Based on discussion with the API-SIG, we determined that if someone sets *_api_version or OS_*_API_VERSION to a value that looks like a microversion, we should pass it to default_microversion in addition to using it for major version discovery. Update the docs to reflect the microversion story (and to remove shade references) Also, throw an error on missing support for default microversion We've given the user the ability to set a default microversion. However, that microversion might not be available on the cloud in question. Throw an error in such cases. Depends-On: https://review.openstack.org/568640 Change-Id: Iad7194dc9e933660c0d0df9130c51d505dda50cb
23 lines
729 B
Plaintext
23 lines
729 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
PyYAML>=3.12 # MIT
|
|
appdirs>=1.3.0 # MIT License
|
|
requestsexceptions>=1.2.0 # Apache-2.0
|
|
jsonpatch!=1.20,>=1.16 # BSD
|
|
six>=1.10.0 # MIT
|
|
os-service-types>=1.2.0 # Apache-2.0
|
|
keystoneauth1>=3.7.0 # Apache-2.0
|
|
deprecation>=1.0 # Apache-2.0
|
|
|
|
munch>=2.1.0 # MIT
|
|
decorator>=3.4.0 # BSD
|
|
jmespath>=0.9.0 # MIT
|
|
ipaddress>=1.0.17;python_version<'3.3' # PSF
|
|
futures>=3.0.0;python_version=='2.7' or python_version=='2.6' # BSD
|
|
iso8601>=0.1.11 # MIT
|
|
netifaces>=0.10.4 # MIT
|
|
|
|
dogpile.cache>=0.6.2 # BSD
|