-
Notifications
You must be signed in to change notification settings - Fork 547
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
Allow fetching TUF root from HTTP #1185
Conversation
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.
@RaD Could you add a test ? So we can validate both use cases.
This PR is related to: #1179 |
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.
@rgerganov You are also missing to update the command description to be able to use a different mirror in cmd/cosign/cli/initialize.go
:
SigStore remote TUF repository is pulled from the GCS mirror at sigstore-tuf-root.
This description is about the default behavior which is not changed (i.e. pulling from GCS) |
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.
Thank you!
This patch allows fetching TUF root from HTTP in addition to GCS. If the specified mirror is an HTTP link, then HTTPRemoteStore will be used. Otherwise it defaults to GCS. Signed-off-by: Radoslav Gerganov <rgerganov@vmware.com>
This patch allows fetching TUF root from HTTP in addition to GCS. If the
specified mirror is an HTTP link, then HTTPRemoteStore will be used.
Otherwise it defaults to GCS.