ContentGuard should be applicable to individual PyPI packages within a distribution/index
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- authorization, backend
Research direction
No files, tests, or entry points are named. Start by locating how distributions, individual PyPI packages, and ContentGuard/RBAC permissions are represented; done requires a defined, tested mechanism for applying a ContentGuard at package scope without requiring a separate distribution per package.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
There is currently no way to control RBAC permissions on an individual PyPI package within a single pulp_python distribution.
Describe the solution you'd like
There should be a mechanism to apply a ContentGuard to not only a distribution, but also to individual PyPI packages within each distribution.
Describe alternatives you've considered
To try to achieve something similar today, you would need to build 1 distribution and 1 RBACContentGuard per 1 PyPI package to achieve a similar outcome. This will lead to a large # of objects to maintain over time. It will also present a future problem if someone creates a 2nd PyPI package on any existing index, since moving the 2nd package to its own index later would result in a URL change for the 2nd package and may break downstream things that are consuming it. Managing the permissions at the PyPI package level would prevent both of these issues.
- Dominant language
- Python
- Stars
- 49
- Forks
- 88
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 31
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.
More from pulp/pulp_python
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
pulp/pulp_python#1381 ·
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 45/100
pulp/pulp_python#1371 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
pulp/pulp_python#1360 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
pulp/pulp_python#1358 ·
-
Feature
pulp/pulp_python#1340 · 1 assignee ·
All issues in pulp/pulp_python
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100