protos: add support for go_option package#17460
protos: add support for go_option package#17460mattklein123 merged 15 commits intoenvoyproxy:mainfrom remyleone:specify_go_package
Conversation
|
Hi @remyleone, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
|
I think we need this now. |
|
@kyessenov I'm ok to do a pass, how can the linter rule be implemented? |
|
@kyessenov pass done. How can we check it up with a linter? |
|
Thanks you for doing this forklift change. I think the linter needs to be fixed here: envoy/tools/protoxform/protoprint.py Line 206 in 79ade4a to add go_package option. You can see how it is done for java. |
|
/wait |
|
@yanavlasov done in envoy/tools/protoxform/protoprint.py :) |
kyessenov
left a comment
There was a problem hiding this comment.
Thanks for the massive cleanup. There's a syntax linter in python script that needs a fix, but otherwise, everything LGTM.
|
/lgtm api |
|
@kyessenov fixed :) |
|
I think the script |
|
Can you try running just the proto formatter locally? |
|
/wait |
|
@keith done :) It modified a lot of files in generated_api_shadow and in API. Is this command documented somewhere? |
|
Hrm looks like formatting failed just for 3 files this time, maybe for unrelated changes. I guess it might be ideal if you could only update the format of the files you intentionally changed, but I'm not sure how folks normally do this if others did need updates. Regardless maybe you can fix those 3 files and be good here? I'm not sure if it's documented or what the normal workflow is here I just found that in the script you tried to run and am hoping that should be all we need |
|
So this looks like an actually related failure? |
|
hi @remyleone looks like this will need a rebase |
|
🙀 Error while processing event: |
Add a linter pass for go_package Fix with ./tools/proto_format/proto_format.sh fix Signed-off-by: Rémy Léone <rleone@scaleway.com>
These updates are required for things to work nicely when building on Apple Silicon machines targeting darwin_arm64. Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
This reverts commit b21ec23906d82ac19be63436e33d74b2f3a83a3d. Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
|
/retest |
|
Retrying Azure Pipelines: |
|
Thanks for slogging through all the protos. |
|
Thanks a lot for the reviews and patience :) |
|
Thanks for all the hard work everyone! |
Hello, I would like first to see if this change is desired before specifying the go_package option in all the files. If so, I will gladly specify it everywhere. :)
For reference when I use envoy in buf I get the following warnings:
#17082