pbr is not a runtime dependency, so there's no need to list it as one.
Similarly, we don't need to install pre-commit in our test environment
nor do we use nose of python-subunit (at least directly). Remove them
all.
We also remove so notes about dependency order that have not been
relevant since the new dependency resolver was introduced in pip 20.3.
Change-Id: Iea7a68dae4c96bc7118e946fc6d494a8799942af
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This bumps the tenacity dependency to
>= 5.0.0 because that is what should have
been done with the fix in [1] where that
new support was added.
[1] https://review.opendev.org/c/openstack/tooz/+/829412
Change-Id: I5aef75c3dba44b975b850c0745bfe317837d2c12
md5 is not an approved algorithm in FIPS mode, and trying to
instantiate a hashlib.md5() will fail when the system is running in
FIPS mode.
md5 is allowed when in a non-security context. There is a plan to
add a keyword parameter (usedforsecurity) to hashlib.md5() to annotate
whether or not the instance is being used in a security context.
In the case where it is not, the instantiation of md5 will be allowed.
See https://bugs.python.org/issue9216 for more details.
Some downstream python versions already support this parameter. To
support these versions, a new encapsulation of md5() has been added to
oslo_utils. See https://review.opendev.org/#/c/750031/
This patch is to replace the instances of hashlib.md5() with this new
encapsulation, adding an annotation indicating whether the usage is
a security context or not.
Reviewers need to pay particular attention as to whether the keyword
parameter (usedforsecurity) is set correctly.
Change-Id: Idbef0f0896753765372c8dfac8ab15e6be49922f
Depends-On: https://review.opendev.org/#/c/760160
Sphinx 2.0 no longer works on python 2.7, so we need to start capping it there.
grpcio-1.16.0 introduced a bug that is breaking the tooz unit tests.
cf. I8b026a0680a91a68281e354a59012565f4db1b95 for more info. 1.18.0
fixes the problem, so bump our minimum requirement to that version.
Change-Id: I4b672563f4a80ce0e0478c867b7f85842ac3b0d3
We have a couple of issues blocking tooz test jobs right now. This
is a combination of two commits that fix the problem.
Cap grpcio<1.16.0
1.16.0 introduces a bug that is causing our etcd3 tests to fail on
a consistent basis. Until that is resolved we can't use any higher
versions of grpcio.
1.0.0 is used as the lower bound on the assumption that any version
of the current major release will work. Since we weren't setting a
bound before that seems relatively safe.
Partial-Bug: 1808046
Fix requirements
The requirements check job is failing on a couple of the entries in
this project. enum34 needs a lower bound, and futurist has an
exclusion that isn't in global-requirements.
enum34 is given the same lower bound as oslo.upgradecheck, and
futurist's lower bound is increased to the last global lower bound
(before lower bounds were removed), which eliminates the need for
the exclusion.
Change-Id: I1b279e138325b596f5ec2c61717029d2f7bdd075
Depends-On: https://review.openstack.org/#/c/624759/
This makes sure we install the correct and only the correct dependencies
when installing tooz, based on the driver one wants to use.
Change-Id: I58825cf228771a00b28d515a552141b42f884efa
For now it only supports locks, in the
future it may support more functionality
as time allows (and/or if people want to
add it).
Co-Authored-By: Joshua Harlow <harlowja@gmail.com>
Implements: bp add-consul-driver
Change-Id: I6064383e9db4e90fd16f17065bd7b0934ca7e125
The voluptuous is easier to use for non-rest oriented
library & services (which is really the place for jsonschema
to be used, as the schema for rest-services can be sent
to the user in json if needed) so use voluptuous internally
instead of jsonschema for simplicity and ease of use.
Change-Id: I0246708a5f8b60a9bedcddd0a8971d7d18eb589a
Using jsonschema we can validate (at a basic level)
that the files created and the contents written were
not altered to be of a different format so add some
basic format validation to help in detecting format
issues/changes.
This also avoids having to use type errors to try to
detect this same kind of tampering/data format change.
Change-Id: I80b4e560f24162e079cf4adab06d35ec75f4b70c