ContentGuard should be applicable to individual PyPI packages within a distribution/index
まだ誰も着手していません。
- 主要言語
- Python
- スター
- 49
- フォーク
- 88
- 平均マージ
- 1日 10時間
- マージ済み PR(30日)
- 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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100