We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please see sigstore/policy-controller#112 for more context.
TLDR - without this being removed, policy-controller will crash on startup due to conflicts with the klog dependency.
This appears to be brought in via github.com/google/certificate-transparency-go. After looking there, it led to a rabbit hole of other dependencies which also rely on glog.
I've opened up the following PRs which may or may not be all of the locations:
An alternative could be for the sigstore org to maintain a fork of glog, just for replace purposes. The required changeset would be this.
The text was updated successfully, but these errors were encountered:
For some context, I tried to work around this issue awhile ago by copying in files from certificate-transparency-go (https://github.com/sigstore/cosign/blob/f2c360eb97e52fa7766ecde370f1a48b910d7404/cmd/cosign/cli/fulcio/fulcioverifier/ctutil/ctutil.go) to avoid pulling in glog.
Sorry, something went wrong.
Seems to be resolved, I don't see a dependency on glog anymore
No branches or pull requests
Please see sigstore/policy-controller#112 for more context.
TLDR - without this being removed, policy-controller will crash on startup due to conflicts with the klog dependency.
This appears to be brought in via github.com/google/certificate-transparency-go. After looking there, it led to a rabbit hole of other dependencies which also rely on glog.
I've opened up the following PRs which may or may not be all of the locations:
An alternative could be for the sigstore org to maintain a fork of glog, just for replace purposes. The required changeset would be this.
The text was updated successfully, but these errors were encountered: