-
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
Updater: mirrors configuration tweaks #1079
Labels
Comments
maybe look at #1077 at the same time? |
Agreed, changing |
Actually the schema system does not make |
jku
pushed a commit
to jku/python-tuf
that referenced
this issue
Sep 25, 2020
Now clients can leave out targets_path or metadata_path if the client knows the mirror does not have that type of targets. This is backwards compatible: old mirror configs continue to work. Fixes theupdateframework#1079 Signed-off-by: Jussi Kukkonen <[email protected]>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the Warehouse/pip use case we are not so much interested multiple actual mirrors but separating the target and metadata hosting to two hosts.
Current Updater mirror configuration is close but not quite up to the task:
I would like to have a way of signaling that a particular mirror should not be used for metadata or should not be used for targets (
'confined_target_dirs': []
does offer that, but only for targets). There's multiple ways to solve this: I'm open to suggestions.The mirrors role (which is unrelated to this but deals with the same problem) solves the issue by having PATH_PATTERNS for both metadata and targets, but for this specific use case it would be enough if metadata_path and targets_path could be set to None. Then I could do this in pip:
This would probably be a trivial change in mirrors.py and should not break any existing users
The text was updated successfully, but these errors were encountered: