openstack/barbican
Code Issues Proposed changes

Use new get_rpc_client API from oslo.messaging

Browse Source 
Use the new API that is consistent with
the existing API instead of instantiating the client
class directly.

This was introduced in release 14.1.0 here [1] and
added into oslo.messaging here [2]

[1] https://review.opendev.org/c/openstack/requirements/+/869340
[2] https://review.opendev.org/c/openstack/oslo.messaging/+/862419

Change-Id: I515004d742ebb85034468a2901a3a887cd2b0480
This commit is contained in:
Tobias Urdin 2023-01-19 20:38:56 +00:00
parent f848fa9b4a
commit 115a8282f6
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
barbican/queue/__init__.py
View File

@ -71,10 +71,9 @@ def get_client(target=None, version_cap=None, serializer=None):
return None
queue_target = target or get_target()
return messaging.RPCClient(TRANSPORT,
target=queue_target,
version_cap=version_cap,
serializer=serializer)
return messaging.get_rpc_client(
TRANSPORT, target=queue_target, version_cap=version_cap,
serializer=serializer)
def get_server(target, endpoints, serializer=None):

2
requirements.txt
View File

@ -10,7 +10,7 @@ oslo.config>=6.4.0 # Apache-2.0
oslo.context>=2.22.0 # Apache-2.0
oslo.db>=4.27.0 # Apache-2.0
oslo.i18n>=3.15.3 # Apache-2.0
oslo.messaging>=5.29.0 # Apache-2.0
oslo.messaging>=14.1.0 # Apache-2.0
oslo.middleware>=3.31.0 # Apache-2.0
oslo.log>=4.3.0 # Apache-2.0
oslo.policy>=3.6.0 # Apache-2.0