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++ (27,997 stars) (5,373 forks)batch import
area/buildhelp wanted

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

Tech stack
pythoncppgrpc
Domain
build 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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Bazel build systemprotobuf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Update the import of py proto library in api/bazel/api build system.bzl to load from the protobuf repository instead of grpc, following the guidance at https://protobuf.dev/news/2024-10-01/. Ensure that the new import path works with the existing Bazel setup. Check for any other files that may reference the old import.
py_proto_library should now come from protobuf · envoyproxy/envoy#40104 | Good First Issue