Webhook post sync/other task completion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Is your feature request related to a problem? Please describe.
We have around 16 pulp replica servers and 1400+ RPM/file repositories. All replica pulp servers pull the content from a master pulp server.
Describe the solution you'd like
A webhook to post after completion of a sync/other task reduces the overhead in the master pulp server.
Describe alternatives you've considered
In a frequency of 5/10 mins interval, we pull the status of the task group completion status from of each of the pulp servers.
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 mapping how sync and other tasks report completion and how replica servers currently poll task-group status; the issue does not name files, tests, or an existing webhook entry point. Done should be a defined webhook notification after the requested task completions, with behavior sufficient to replace the described periodic polling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100