Refactor #31300
open
the user shouldn't have to specify the file size when uploading chunks
Added by Evgeni Golov about 4 years ago.
Updated 3 months ago.
Description
Currently, the workflow to upload a file to a repository is the following:
1. call content_uploads/create with file size and repo_id
2. call content_uploads/update in a loop with the content_upload_id, the actual chunk content, the offset of the chunk and the file size
3. call repositories/import_uploads
4. call content_uploads/destroy
I find the requirement to pass the file size in every chunk upload confusing. I've provided it already when I created the upload in step1, so I'd expect Katello to just reuse that value (it won't change anyways).
Related issues
1 (1 open — 0 closed)
- Related to Tracker #27680: API bugs that need workarounds in foreman-ansible-modules added
- Target version set to Katello 4.0.0
- Triaged changed from No to Yes
- Target version changed from Katello 4.0.0 to Katello 4.1.0
- Target version changed from Katello 4.1.0 to Katello 4.2.0
- Target version changed from Katello 4.2.0 to Katello 4.3.0
- Target version changed from Katello 4.3.0 to Katello 4.4.0
- Target version changed from Katello 4.4.0 to Katello 4.5.0
- Target version changed from Katello 4.5.0 to Katello Backlog
from samir:
The upload chunk is an update call on the upload api in pulp3 with upload_href which takes a content_range(offset, offset + actual_chunk_size - 1, size) param as required value which needs to know the size of the file. I couldn't think of any workarounds to this other than querying the pulp api for size on upload or keeping some sort of db in katello.
https://docs.pulpproject.org/pulpcore/restapi.html#operation/uploads_update
it does need it, sure, but can't Katello calculate it? the same way it happens if the upload happens via the UI which does not have a "size" field ;)
- Target version deleted (
Katello Backlog)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by