Story #4988
closed
As a user, I can remove uploads
Status:
CLOSED - CURRENTRELEASE
Description
Example:
http POST :24817/pulp/api/v3/uploads/ size=10485759 # returns a UUID (e.g. 345b7d58-f1f8-45d9-d354-82a31eb879bf)
export UPLOAD='/pulp/api/v3/uploads345b7d58-f1f8-45d9-d354-82a31eb879bf/'
http DELETE :24817${UPLOAD}
Allow any upload to be deleted. Also, add a filter to list incomplete uploads.
- Related to Story #4196: As a user, I can upload files in chunks. added
- Related to Story #4981: Remove incomplete chunked uploads after a set amount of time added
- Subject changed from As a user, I can remove incomplete uploads to As a user, I can remove uploads
I'm setting this to being blocked by #4488 since #4488 changes the chunked upload code/API.
- Blocked by Story #4488: As a user, I can upload chunks in parallel added
- Tracker changed from Issue to Story
- % Done set to 0
I think it can be deleted if the upload is complete.
I'm more worried about incomplete ones and how to determine that it's safe to delete them. I'll comment on #4981.
I lean towards allowing users to delete any uploads including incomplete ones. To me, uploads are transient so I don't worry about users accidentally deleting ones. I guess I worry more about users not being able to easily remove large amounts of data from their filesystem.
Users should be able to delete any Upload.
- Groomed changed from No to Yes
I think it's ok for now. In case users report that it's easy to accidentally remove it in their workflow, we can introduce a flag like "force=True".
- Description updated (diff)
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 3.0.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Allow deletion of uploads
Also added a filter to filter by incomplete.
fixes #4988