-
Notifications
You must be signed in to change notification settings - Fork 275
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
client/updater design: mirror config redesign #1143
Comments
Current TUF Updater mirror config means queries to the wrong server: theupdateframework/python-tuf#1143 Workaround by storing two separate mirror configurations: one for index file downloads and one for distribution file downloads.
Current TUF Updater mirror config means queries to the wrong server: theupdateframework/python-tuf#1143 Workaround by storing two separate mirror configurations: one for index file downloads and one for distribution file downloads.
After further meditation: this particular issue cannot be fixed in TUF client. Even if confined_target_dirs allowed subdirectory matching, pip could not use them to separate index files and distribution files: The directory names "simple" and "packages" are just implementation details of pypi.org, not part of the Warehouse API. Some other instance might use the same directory name on both servers. This is essentially a result of not namespacing the target names of index files and distribution files in the Warehouse TUF implementation: it is impossible to tell the two targets apart without some heuristics. |
Current TUF Updater mirror config means queries to the wrong server: theupdateframework/python-tuf#1143 Workaround by storing two separate mirror configurations: one for index file downloads and one for distribution file downloads.
Mirrors have been annihilated in new client:
|
This is a future wishlist item for client API (#1135), based on working on pip integration. I'm not sure what exactly should happen here, just documenting the issues
Warehouse may be an unusal setup but here's how it works (using server names of the pypi instance as examples):
Issues encountered while implementing a client for this:
This could be fixed in TUF... but reality is that pip does not really need a mirror config: it always knows which server it wants to use for a particular download. With current API this means I will end up storing two mirror configurations and choosing the correct one every time before a download happens.
The text was updated successfully, but these errors were encountered: