delta/python-packages/tooz.git/tooz/drivers/pgsql.py, branch master

Replace md5 with oslo version

2020-10-29T19:44:36+00:00

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

Remove six library

2020-07-01T13:56:53+00:00

The tooz project doesn't support Python 2 anymore, using the
six library should not be necessary.

Change-Id: I9886cabcd13cbc615065ceb372efbf037dff1aeb

More explicitly document driver connection strings

2018-12-17T22:37:55+00:00

If you're not intimately familiar with RFC 1808 it can be a bit tricky to
write tooz connection strings. In addition, some drivers do not document the
options that they recognize in a connection string. This can force a user to
read the driver code in order to figure out how to configure tooz to use said
driver, which should not be the case.

This change more explicitly documents the format of the connection string,
including which parts of an RFC 1808 URI it recognizes, and the options that
can be passed. It also clarifies which parts of the connection string are
optional (possibly because they have defaults) and which must always be
included.

Note that not every possible configuration is documented. For example, the
postgres driver supports multiple methods of configuring the connection host
and port. For consistency, I only documented the one that matches the other
drivers. This should be sufficient to allow a user to write a working
connection string.

This change also wires the etcd3 and etcd3gw drivers into the doc index since
they were missing before.

Change-Id: I66e54433115f27fb54badc2173f8f6044c49aacb

Merge "Mutualize executor code in a mixin class"

2017-06-24T06:40:36+00:00

pgsql: fix self._conn.close() being called without connection

2017-06-22T10:48:06+00:00

If an error occurs on connection establishment, self._conn is None so it can't
be closed.

Change-Id: If6fce24cb27aa7090b5165ca4a895c846c40d2dd

Mutualize executor code in a mixin class

2017-06-21T15:43:26+00:00

Change-Id: I364b0ca5a6361a818a084bbcb83c9e7855cb3583

{my,pg}sql: close connections when out of retry

2017-06-16T11:40:42+00:00

The connection is supposedly closed when blocking is False and the lock is not
acquired. Or when an exception happens in the locking code.

But if blocking is e.g. 5 seconds, then RetryError is raised but without
closing any connection at the end. This fixes that.

Change-Id: I7b40e466fe5fc01ee3f8c012f765aafca9ce716a

Merge "Fix psycopg2 connection argument"

2017-05-09T19:44:41+00:00

Fix psycopg2 connection argument

2017-05-08T21:30:04+00:00

commit 6eea97c3efe6dee6c2c036a581354aaa9b8ef5fa modified the kwarg from "user"
to "username" by mistake.

Change-Id: Idfe8425d08c065ef19e8952e8fcb205779243a99
Closes-Bug: #1689211

sql: close connection for lock if not used

2017-04-27T14:27:30+00:00

each lock creates it's own connection and only gets released when
garbage collection kicks in because of limitations

change logic so if we don't have lock, we don't have connection.

Change-Id: Ibf6eaf3ff3031424917e9fdb6920bf2fc1808b7c