Handle Artifact creation inside tasks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Artifact creation requires some considerable i/o processing (such as calculating checksums), which can create a higher than desirable load on the API service.
Also, if a plugin requires to do pre-processing of an uploaded file, it can't do it inside a task, as the Artifact would already be created inside SingleArtifactContentUploadViewSet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SingleArtifactContentUploadViewSet in pulpcore/plugin/viewsets/content.py, especially the linked upload handling. Trace where Artifact creation and checksum processing occur, then determine how creation can run inside tasks while allowing plugins to preprocess uploaded files. Done means the API service avoids that processing and plugin preprocessing can happen before the Artifact is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100