-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure _getBackbeatClient Always Returns BackbeatMetadataProxy #2439
Conversation
Hello nicolas2bert,My role is to assist you with the merge of this Status report is not available. |
ping |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.5/bugfix/BB-431/get-backbeat-client origin/development/8.5
$ git merge origin/w/7.70/bugfix/BB-431/get-backbeat-client
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.5/bugfix/BB-431/get-backbeat-client |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.6/bugfix/BB-431/get-backbeat-client origin/development/8.6
$ git merge origin/w/8.5/bugfix/BB-431/get-backbeat-client
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.6/bugfix/BB-431/get-backbeat-client |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
@bert-e approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-431. Goodbye nicolas2bert. |
The
_getBackbeatClient
function from theBucketProcessor
should consistently return an instance ofBackbeatMetadataProxy
. However, there is an issue in the code where the function returns an instance ofBackbeatClient
when caching.Impact:
Ring S3C: no direct impact today, since
backbeatClient
is only used for "lifecycle Transition workflow" that has been backported but is not supported yet. However, the inconstant result of_getBackbeatClient
blocks additional development such as “lifecycle listing optimization “.Artesca: no impact since the logic has been fixed already with the ClientManager: https://github.com/scality/backbeat/blob/development/8.7/lib/clients/ClientManager.js
Note: the getBackbeatClient from the ObjectProcessor is correctly implemented.