Skip to content

s3: batch published pool cleanup - #1614

Open
arges wants to merge 1 commit into
aptly-dev:masterfrom
arges:arges/batch-pool-cleanup
Open

s3: batch published pool cleanup#1614
arges wants to merge 1 commit into
aptly-dev:masterfrom
arges:arges/batch-pool-cleanup

Conversation

@arges

@arges arges commented Aug 4, 2026

Copy link
Copy Markdown

Fixes #1613

@codecov

codecov Bot commented Aug 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.16%. Comparing base (f59b0d2) to head (6079ff7).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1614      +/-   ##
==========================================
- Coverage   77.37%   77.16%   -0.22%     
==========================================
  Files         165      165              
  Lines       15747    15799      +52     
==========================================
+ Hits        12185    12191       +6     
- Misses       2356     2407      +51     
+ Partials     1206     1201       -5     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Use S3 multi-object deletion for orphaned published pool files, while retaining
per-file deletion for other storage backends.

Signed-off-by: Chris J Arges <carges@cloudflare.com>
@arges
arges force-pushed the arges/batch-pool-cleanup branch from 3302111 to 6079ff7 Compare August 5, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

s3: object deletion when removing a published repo is slow

1 participant