The changes here are all small enough to be bundled into one.
Change-Id: Ia585244e314a9bd18a7cd2388a2936517e25dbf2
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This one is cool. We use overload to allow the value of 'Resource.find'
and 'Proxy._find' to vary depending on whether 'ignore_missing' is True
or False.
Change-Id: I386e10774dfb6ec9db80cbda9757446a2b5e4e57
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Yet another bug here: we weren't passing 'session' arguments.
Change-Id: Id9c5bafe8bc71024ff6d453870553dd45b6576d1
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Another small bug to be corrected here: SDKException does not have a
'response' attribute.
Change-Id: I084336ba41147f824b92dc07235e5f19b7ac4a9c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Just an incorrect type annotation to correct here. We need to figure out
a way to properly type the 'Resource' class with all its magic.
Change-Id: Id238b870de85a4663032710d1c15f6e200d2d543
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Another bug highlighted. A test will come later so as not to confuse
this patch.
Change-Id: I38f1a3911781470b77644cd42512408f8c03dc4d
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Our first significant bug! We were registering the 'group_type' module
rather than the 'GroupType' resource in our block storage v3 proxy's
resource registry. This is corrected. The rest of the changes are simply
to work around mypy (obviously) not being able to detect the key and
value types for empty dicts. Cinder doesn't care about the values of the
dict for most WSGI actions so this doesn't matter.
Change-Id: I4d9a4d4fcf08e8aa13b47314b24b2bb7226be3eb
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This was in-effect already dropped with the introduction of the
dependency on platformdirs > 3.0. This just makes it official.
Change-Id: I18806e78fe1491948948d224edb27d6ac4a8f45f
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Note that mypy is the last item in the list of checks since flake8 is
going to catch e.g. syntax issues which should be addressed first.
Change-Id: Id58fb9e8ea454c10e502c96ad4c36788e7533318
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I6974592dc7cd44a749986ec0373afddc48d43b78
Now that we released ussuri, we have a stable release that supports
3.5. That means if needed we can backport changes needed for
zuul and nodepool, so it should be safe to go ahead and drop 3.5
support.
Change-Id: Iaa761cb6f6ab30fa26f6587ac29f11274702e1a3
Introduce support of python 3.8 and move tox and jobs to py38.
jsonschema 3.2.0 [1] support python 3.8
[1] https://github.com/Julian/jsonschema/pull/627
Change-Id: Ibcfa044dd0f3b29fd290559795ea1d98e194e886
Remove requirements only needed by Python prior to version 3.5.
Remove python 2.7 code from setup.py.
Remove from setup.py ancient sections.
Change-Id: Ie223b743a0f8def53874bfbbb5f9000ad26f030b
We require 3.5 now but we didn't add the metadata. Add it.
While OpenStack broadly only supports 3.6, openstacksdk
has a wider audience, including nodepool which still uses
3.5. So add the 3.5 unit tests back.
Use lower-constraints for py35 unit tests because the
upper-constraints have versions of things that have
droppped py35 support already.
Depends-On: https://review.opendev.org/#/c/715467/
Change-Id: I680e0bab5ba3af7be5e914ece64c6bd25d1f2191
We're peeling python2 from libraries now, so Stop running python2
versions of test jobs. Leaving removing the test jobs themselves
for the moment as they're still used in other repos.
Change-Id: Ic6d56e3636b757201d83649f075005ed3ae1e1a6
The openstacksdk docs are published at docs.o.o, not developer.o.o since
quite some time. Fix links to point to current version of docs.
Add missing links, thus removing some TODOs.
Change-Id: I5e3b4c70bc0875a1dfcc587b60a95258a61b4407
Now that the repo is renamed, update all of the references.
While we're at it, remote unused translation config.
Change-Id: Ib9f80eb809317483f83f79952470c2b57b2bb7c6
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: If2aba189704c310ea4fcb805589e2732a525e992
Now that there is a passing gate job, we can claim
support for Python 3.5 in the classifier.
This patch also adds the convenience py35 venv.
Change-Id: I5c5cdf59c32052e051fe3c586074aec7c5f2347f
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I2147b18fd9ecc32eef3c8670e33def2a702e7d20
Prepare for the next release and set the package name to openstacksdk
and drop the python- prefix. This package name has already been reserved
on PyPI.
This was initially started by a discussion at the summit around
OpenStackClient making the same move to strip the python- prefix
(they haven't completed it, but have reserved the PyPI name).
It was further discussed on IRC and I believe in a meeting that
there is no benefit to having the python- prefix here. There is
no name collision we're avoiding with it, and it provides
nothing extra by being prefixed as such.
Change-Id: I1145883a2f896769143a3fcc6e43468d6e590e11
Way back at the Summit I said I'd revert back to the standard
KSC auth plugins. Well here, they are.
Change-Id: I8acc2be3f2ac7d10b6914f892d9f0bfe734496fd
This change updates the README text that shows up on PyPI so we can get
a small example up there as well as the documentation link. It also
marks 3.4 as supported, since we've been testing that for a while now.
Change-Id: I28555eb4e121f35151afc8548adb3df166257814
Closes-Bug: 1420858
Move the version detection code into a plugin because it
does not belong in connection. Create a new discoverable plugin
that looks at the auth_url and makes a best guess if it should
use v2 or v3 auth.
The plugin also now accepts access_info so a cached version
of the authorization can be reproduced without hitting
keystone.
Change-Id: Ia5d32457c90716627a75be2c99267c4ed7903197
Stephen Finucane