As a user, the orphan cleanup endpoint will support Role Based Access Control
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @bmbouter (bmbouter)
Redmine Issue: 7337, https://pulp.plan.io/issues/7337
By default no users will be able to run orphan cleanup. This is reasonable because systems opt-in to RBAC by using non-admin users, so installs with 'admin' users will bypass this default policy.
One new permissions will be created. This will not be associated with any specific model, either a user has it or they don't.
- ("execute_orphan_cleanup", "Can execute orphan cleanup"),
The orphan cleanup view will require this permission to execute.
This view will not provide any queryset filtering as there are no orphan_cleanup views.
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
Locate the orphan cleanup view and the project's permission definitions. Check how standalone permissions are registered, then trace the view's authorization path. Done means the execute_orphan_cleanup permission exists, the view requires it, and no queryset filtering is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100