envoyproxy/envoy

py_proto_library should now come from protobuf

Open

#40,104 opened on Jul 3, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/buildhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Per https://protobuf.dev/news/2024-10-01/ the protobuf repo will be the source of the py_proto_library rule. This ticket covers updating envoy (and in particular, api/bazel/api_build_system.bzl) to load py_proto_library from protobuf instead of grpc.

See https://protobuf.dev/news/2024-10-01/

Contributor guide

Research direction
Update the Bazel load statement to load py proto library from @protobuf instead of @grpc in api/bazel/api build system.bzl. Verify that the rule is available in the protobuf repository and adjust any dependencies.
Tech stack
python
Domain
backendbuild system
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75