Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is there a setup possible that allows whitelisting from one base but not the other? #933

Open
krpatter-intc opened this issue Nov 1, 2022 · 3 comments

Comments

@krpatter-intc
Copy link

Is it possible to add intermediate indexes such that I could effectively create a different whitelist based on the base (or mirror in this case) ?

In this scenario: helloworld==1 might be on root/something-else, and helloworld==2 is on production, but we want to make sure to not accidently grab helloworld from root/pypi

flowchart TD
    production --whitelist=* --> root/something-else
    production --whitelist=none--> root/pypi

If the "why" matters: I was hoping offload really old releases from our devpi server to a different server. This would save disk space on my primary server my replicas. Sure they may mirror the versions most needed, but it wouldn't be N replicas with ALL the old versions.

Any ideas/feedback would be appreciated. Thank you.

@fschulze
Copy link
Contributor

fschulze commented Nov 2, 2022

Currently I can't think of a way to achieve this. The more I think about it the more I come to the conclusion, that mirror indexes currently are still stuck in the original PyPI only mode. It would make sense that they work more like private indexes in regard to bases etc, so they can have parents and not only be roots.

So your setup would look like this:

flowchart TD
 production --whitelist=* --> root/something-else --whitelist=none --> root/pypi

Not entirely sure this wouldn't open another can of worms in regard to whitelist and filtering etc.

@krpatter-intc
Copy link
Author

That's what I feared, but thank you for the quick response.

@fschulze
Copy link
Contributor

fschulze commented Dec 5, 2022

Reopening for future consideration.

@fschulze fschulze reopened this Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants