As an admin of a domain-ized system, I can use an un-domain-ized tasking API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
We admin a Pulp system which has hundreds of domains, e.g. ~600. Recently we wanted to look at the tasking system via API to see how many tasks were in the waiting state. Is it right that we can only do that per domain? If so, we need some way to get the total picture in a more practical sense.
So more or less: As an admin I can have the un-domain-ized tasking API endpoint available on domain-enabled installations.
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 locating the tasking API entry point and the code that applies domain scoping. Confirm how administrators access task data on domain-enabled installations and whether an un-domain-ized view is currently available. Done means an administrator can retrieve an overall tasking view, with tests covering the domain-enabled behavior.
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
- 35/100