Document permissions needed for listing deb releases, release components, etc.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
We're trying to use a non-admin user to list and create deb repository releases, release components, packages, and package release components, but keep getting 403s even after giving the account deb.apt{repository,distribution}_owner on the needed objects. I don't see any roles (we're on 3.73) that even reference those things. What permissions are actually needed to list and/or create those?
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
Review the existing role definitions and permission checks for deb releases, release components, packages, and package release components, starting from the plugin's permission configuration or API entry points. Verify the permissions required to list and create each resource for a non-admin user, then document the results. No file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100