Repository navigation
Conversation
|
There is something in the works for this already. Your suggestion gave me a good idea for simplification of that. Thanks! I'll keep this open until it lands on master. |
|
@fschulze Wondering if there is still ongoing work for this feature and what's the roadmap, it would be greatly useful for our workflow |
|
The server side is in the latest devpi-server and devpi-lockdown releases, but the client side still needs further testing and a release. One also needs to write a plugin with custom hook implementations which I will most likely put in a gist as an example. With that a whole index can be restricted, individual projects have too many interactions with other parts to be easily restricted without unwanted side effects or leaks. |
|
The client side changes have been merged for the upcoming devpi-client 6.0.0. The hooks could look like this: If you want the lockdown to spread to inheriting indexes, add this hook as well: As this still isn't a perfect lockdown I won't add this to an existing plugin or create a new one. Everyone has to test this for their own circumstances. For example the devpi-web search can leak names and there is most likely other stuff I currently forget. |
Hello,
please, add permissions for reading packages (aka "projects", if i get it right).
it's really needed to set user-based access to packages further (via plugins).
ps. if you find "pkg_read" is not ok, lets call it "read_project" (based on another existing permission name -"del_project") or so.