-
Notifications
You must be signed in to change notification settings - Fork 55
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
tough: support the loading of an expired repo in unsafe mode #121
Conversation
1785e90
to
8d192c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Two things:
- This is a API-breaking change so we'll want to make sure that we bump the minor version of the entire library and update the changelog.
- We'll probably want to add an argument to
tuftool
so a user can download an expired repo. This is also an API breaking change and deserves a version bump.
Let's get @iliana 's eyes on this too. :)
Agreed. The versions are already bumped to 0.5.0 and I plan to write the changelog in a separate release PR.
Yes, that could be added separately if we want the functionality exposed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can move my feedback into an issue. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
🏎️
Issue #, if available:
Closes #112
Supports bottlerocket-os/bottlerocket#905
Supports bottlerocket-os/bottlerocket#91
Description of changes:
Add a setting to the
Settings
object such that we can choose to load a repository with expired metadata if we want to. This supports a use case in Bottlerocket when we need to load a cached, local repository without access to networking, and where failing due to an expiration cannot be tolerated.I used an enum for this setting,
Unsafe
vsSafe
to make it clearer what this setting does, and thus harder to accidentally choose incorrectly.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.