ContentGuard should be applicable to individual PyPI packages within a distribution/index
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- python
- Área
- authorization, backend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 49
- Forks
- 88
- Merge medio
- 1 d 10 h
- PR fusionados (30 d)
- 31
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pulp/pulp_python
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
pulp/pulp_python#1381 ·
-
Feature Triage-Needed
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
pulp/pulp_python#1371 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
pulp/pulp_python#1360 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
pulp/pulp_python#1358 ·
-
Feature
pulp/pulp_python#1340 · 1 asignado ·