pulp / pulp/pulp_python

ContentGuard should be applicable to individual PyPI packages within a distribution/index

未关闭
#727 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

Feature
主要语言
Python
星标
49
派生
88
平均合并
1 天 10 小时
30 天内合并 PR
31

描述

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.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

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.

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
authorization, backend
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。