envoyproxy/envoy

reconcile matching throughout Envoy config/API

Open

#5,569 opened on Jan 11, 2019

View on GitHub
 (8 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
api/v3area/securityhelp wantedtech debt

Repository metrics

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

Description

We have a lot of different matching going on (route, RBAC, Tap, filter chain, etc.) and we probably could share more matching infrastructure across components. This issue tracks figuring out a plan to see what can be shared.

Contributor guide

Research direction
Investigate current matching implementations across Route, RBAC, Tap, and filter chain components. Document shared patterns and identify opportunities for unification.
Tech stack
cpp
Domain
backendinfrastructurenetworking
Issue type
Research
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.
Over 1 week
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++Envoy architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25