envoyproxy/envoy

Feature disparity between gRPC bridge and gRPC reverse bridge

Open

#16,672 opened on May 26, 2021

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

Repository metrics

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

Description

Title: Feature disparity between gRPC bridge and gRPC reverse bridge

Description:

Currently there's a bit of config/feature disparity between these 2 filters, where the reverse bridge offers more functionality. It would be great to support the same config options in the gRPC bridge as well. For example bridging a application/x-protobuf HTTP 1.1 request without the gRPC header frame and responding with the same content type and without the gRPC header frame.

Contributor guide

Research direction
Study the configuration of the gRPC reverse bridge and identify which options are missing in the gRPC bridge. Then implement those options in the bridge filter.
Tech stack
cppgrpc
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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
C++gRPCEnvoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55