Story #4981
Remove incomplete chunked uploads after a set amount of time
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:
0%
Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Description
Chunked uploads could be large. If they are never turned into artifacts, they could take up large amounts of disk space indefinitely.
Related issues
History
#1
Updated by daviddavis 12 months ago
- Related to Story #4196: As a user, I can upload files in chunks. added
#2
Updated by daviddavis 12 months ago
- Description updated (diff)
#3
Updated by daviddavis 12 months ago
- Tracker changed from Issue to Task
- % Done set to 0
#4
Updated by daviddavis 12 months ago
- Tracker changed from Task to Story
#5
Updated by daviddavis 12 months ago
- Related to Story #4988: As a user, I can remove uploads added
#6
Updated by ttereshc 11 months ago
Does it make sense to extend the upload API for GET and DELETE and accept the parameter incomplete=true?
So one would be able to list or retrieve incomplete uploads and remove them by explicitly specifying that they are removing the incomplete one.
E.g.
# all
http GET :24817/pulp/api/v3/uploads/ incomplete=true # or just filter by completed_at
# specific one (not very useful but might be a way to check for a user if the upload is incomplete or not)
export UPLOAD='/pulp/api/v3/uploads/345b7d58-f1f8-45d9-d354-82a31eb879bf/'
http GET :24817${UPLOAD} incomplete=true # or just filter by completed_at
# remove a specific one
http DELETE :24817${UPLOAD} incomplete=true
#7
Updated by daviddavis 9 months ago
- Sprint/Milestone deleted (
3.0.0)
Please register to edit this issue
.