Sync pipeline should provide a way for plugins to interact with content and downloaded artifacts before they are put in storage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
By example: A plugin may want to check signatures on packages (say RPM or Debian packages) during the sync process, but when artifacts are downloaded they are quickly shipped off to the storage backend afterwards, which may be Azure/S3. There should be a way for plugins to define checks on downloaded artifacts (and also content) prior to putting them in storage, because accessing them afterwards would incur extra financial and performance cost.
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 by tracing the sync pipeline from plugin interaction through artifact and content download to the storage backend. Identify existing extension points and how plugins access downloaded data before storage. Done would mean an agreed design and implementation path for pre-storage checks that avoids an extra storage read.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100