-
Notifications
You must be signed in to change notification settings - Fork 107
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
feat: Tap 4 Implementation (TUFClient interface) #431
Conversation
I had some issues rebasing with just these commits as I had already started to implement some of your suggestions locally, hence the new PR. |
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.
other than the usage of verifydigest, lgtm
1485d0c
to
57dad58
Compare
This looks good expect for two things:
|
d82c38a
to
d6276c8
Compare
Sorry about this @dibrinsofor but can you rebase? We can do a quick re-review, should be an easy change then. |
b9a5740
to
b068fab
Compare
@znewman01 all done! |
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.
CC @asraa for an extra maintainer approval
See #348
Release Notes:
Types of changes:
!
, as infeat!: change foo
).Description of the changes being introduced by the pull request: Began abstracting Client into interface in interface.go for future use towards multi-client mapping. currently setup with Update, Download, VerifyDigest, Target and Targets functionality. with @znewman01 and @vaikas
Please verify and check that the pull request fulfills the following requirements: