envoyproxy/envoy

Refactor Listener configuration

Open

#8,391 opened on Sep 26, 2019

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

Repository metrics

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

Description

As per the #next-major-version tag in lds.proto, we want to create a new listener structure for v3. I think this should be done in v2, with the creation of some NewKindOfListener resource and the existing Listener tagged as deprecated at message level. Following this, we can have v3 acting as the deprecation tick to remove.

Contributor guide

Research direction
Review the existing Listener message in lds.proto and design a new listener structure. Create a new protobuf message for NewKindOfListener and mark the existing Listener as deprecated. Then implement the v3 changes to remove the deprecated message.
Tech stack
None
Domain
backendnetworking
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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
C++EnvoyProtocol Buffers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30