search

scality / backbeat

Zenko Backbeat is the core engine for asynchronous replication, optimized for queuing metadata updates and dispatching work to long-running tasks in the background.
https://www.zenko.io
Apache License 2.0
53 stars 19 forks source link

BB-380 Add excluded-data-store-name listing parameter #2385

Closed nicolas2bert closed 1 year ago

nicolas2bert commented 1 year ago

If transition rules are configured with a shared storage class and prefix, Backbeat Lifecycle Bucket Processor will exclude keys that have already been transitioned (i.e stored in the (shared) storage class).

Backbeat Lifecycle Bucket Processor uses the lifecycle listing APIs with the excluded-data-store-name parameter to filter out keys that have already been transitioned.

bert-e commented 1 year ago

Hello nicolas2bert,

My role is to assist you with the merge of this pull request. Please type @bert-e help to get information on this process, or consult the user documentation.

Status report is not available.

bert-e commented 1 year ago

Incorrect fix version

The Fix Version/s in issue BB-380 contains:

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

Please check the Fix Version/s of BB-380, or the target branch of this pull request.

bert-e commented 1 year ago

Incorrect fix version

The Fix Version/s in issue BB-380 contains:

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

Please check the Fix Version/s of BB-380, or the target branch of this pull request.

bert-e commented 1 year ago

Incorrect fix version

The Fix Version/s in issue BB-380 contains:

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

Please check the Fix Version/s of BB-380, or the target branch of this pull request.

rahulreddy commented 1 year ago

/bypass_author_approval

bert-e commented 1 year ago

In the queue

The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.

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 the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.

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 member of the admin team now.

The following options are set: bypass_author_approval

bert-e commented 1 year ago

I have successfully merged the changeset of this pull request into targetted development branches:

The following branches have NOT changed:

Please check the status of the associated issue BB-380.

Goodbye nicolas2bert.