-
Notifications
You must be signed in to change notification settings - Fork 162
Revoke dependency leads to broken import of google.golang.org/grpc/naming #76
Comments
It looks like the workaround (until upstream is fixed) is:
|
Thanks @hdm! Tagging in @nicksteele to collaborate on the best way to fix this issue. |
This issue is still unresolved. It would be nice to be able to remove the dependency of the problem ... |
Is there maybe an equal lib like cloudflare's that doesn't introduce such a large dependency tree? Or maybe we could fork the revoke module? The problem is that Go 1.18 is much more strict about dependencies and the original workaround does not seem to work any more. It's also problematic when the project consumes grpc and needs a specific (higher version). |
I think the forking idea may be the best one, though it's not entirely easy. That lib is horrible. The only usage of the model is in metadata to check the validity of devices via their certs as you have probably identified. |
I have run into a similar problem. I created a fork of CFSSL that has just enough functionality for this project. I have changed only import paths in the code and deleted unnecessary things, so that practically no dependency comes with it. |
@Isolus Nice work! Would you be able to open a PR to switch the dependency? |
PR with forked cfssl is #150. It would be nice to merge or maybe duo-labs should provide similar fork in their own repo? |
A long chain of dependencies is introduced via revoke's CT support. This currently leads to a broken module dependency for GRPC:
Edit: It looks like revoke's validation is needed here. Any suggestions for fixing this dependency issue?
The text was updated successfully, but these errors were encountered: