envoyproxy/envoy

Add support for basic gRPC API Configuration YAML files for gRPC-JSON transcoder

Open

#5,507 opened on Jan 7, 2019

View on GitHub
 (6 comments) (3 reactions) (1 assignee)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

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

Description

Sometimes the requirement to have to annotate our .proto files to expose them can be inconvenient. Google cloud provides an alternative approach where we specify our HTTP to gRPC mappings in gRPC API Configuration YAML file rather than in .proto. So is configuration with yaml files supported for gRPC-JSON transcoder in envoy? Or maybe it will be supported later?

Contributor guide

Research direction
Investigate the gRPC API Configuration YAML specification and how Envoy currently handles gRPC JSON transcoding via proto annotations. Determine if there is existing support or a need to implement a new config parser.
Tech stack
cpp
Domain
apibackend
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.
1-2 days
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
gRPCEnvoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20