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
Switch to new Go protobuf v2 module #524
Comments
+1 for this. We looked into this previously and I believe the action items were:
Here's an issue for reference: #403 I can try and help out with this @jpeach but I'm not super skilled/familiar with bazel. I can stumble my way around if you do need me to tackle something though |
Oof, that does not look promising ... |
Yea... this is a big rabbit hole I went down a while back, might be worth revisiting though |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This should be fixed with rules_go v0.33.0: bazelbuild/rules_go#2522 (comment) |
I have a PR open for this now: envoyproxy/envoy#21790 |
Okay looks like this pr: envoyproxy/envoy#21790 got merged so we can now proceed here. @jpeach would you be interested in picking this back up? |
I can probably take a look in a week or so. |
Would like to know if we will resolve this issue together with this PR? |
There's only one place where we use the protobug APIs, so switch to the v2 protobuf module. This updates envoyproxy#524. Signed-off-by: James Peach <jpeach@apache.org>
There's only one place where we use the protobuf APIs, so switch to the v2 protobuf module. This updates envoyproxy#524. Signed-off-by: James Peach <jpeach@apache.org>
There's only one place where we use the protobuf APIs, so switch to the v2 protobuf module. This updates #524. Signed-off-by: James Peach <jpeach@apache.org>
Upstream switched to a new Go protobuf module, protobuf v2. go-control-plane should fully switch over to this so that client projects can switch too. I think the main change that will be needed is to switch the protoc toolchain over to generate wrapper code with the new module.
The text was updated successfully, but these errors were encountered: