-
Notifications
You must be signed in to change notification settings - Fork 517
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
Transition to use golang/protobuf to support automated code generation #226
Conversation
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Needed to be compatible with internal build rules. Signed-off-by: Teju Nareddy <[email protected]> Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
@@ -1,3 +0,0 @@ | |||
[submodule "data-plane-api"] | |||
path = data-plane-api | |||
url = https://github.com/envoyproxy/data-plane-api |
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.
?? why remove this?
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.
The stubs will be pushed from envoy repo directly. I want to have the first commit done manually before I automate the pushes since we still need to validate go module build (which bazel doesn't do).
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.
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.
I'm not following with the changes so just some questions to learn about the change, do we need to run generate_go_protobuf.py
manually to generate all these go files in this repo? Or is it done by some bots automatically? If so how often is it pushed? Thanks
This PR was done by manually running the script. The automation is a follow-up. The script will be triggered by any change to APIs. |
@kyessenov I am trying this out with my sample control plane which was working before this change.
Is there an easy way to fix this? |
Name every import, e.g. import (
auth "github.com/envoyproxy/go-control-plane/envoy/api/v2/auth"
) |
@kyessenov
|
Please use |
Thank you @kyessenov . While I was migrating all usages of gogo to golang, my project's
Is it something because of this ? or is it a mistake on my part? |
It could be, but I'm not an expert in the interplay between glide and go mod. If you have a suggestion, we can merge a fix here. |
@kyessenov You've been immensely helpful and we could finally migrate from go-control-plane v0.8.0 to v0.9.0. |
Fixes #213
Warning This is a breaking change due to the switch from gogo/protobuf to golang/protobuf. Please use branch gogo if you would like to continue using gogo/protobuf.