fix: pin genproto to specific version to avoid envoyproxy/go-control-…

[uri200]

…plane update

Signed-off-by: Oriol Batalla obatalla@fb.com

Summary

We are using envoy 0.9.4 on Magma. That version seems to be using specific versions of grpc and protobuf module.s

To update envoy/go-control-plane we need to refactor the code because the newest versions have a total different API.

So in order to be able to use some new modules on magma we need to pin genproto version to prevent envoy/go-control-plane to automatically update on go.mod and break.

Note in the near future this will break and envoy will need to be either updated or placed on a separate module.

Test Plan

make precommit

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

feg-workflow

    2 files  202 suites   32s ⏱️
363 tests 363 ✔️ 0 💤 0 ❌
377 runs  377 ✔️ 0 💤 0 ❌

Results for commit 9e1ec08.

[emakeev]

LGTM