envoyproxy/envoy

Reconcile filter state and dynamic metadata

Open

#4,929 opened on Oct 31, 2018

View on GitHubContributor guide
 (8 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
help wantedtech debt

Repository metrics

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

Description

See started PR here as well as discussion: https://github.com/envoyproxy/envoy/pull/4873

At minimum we need clear docs on when to use each one. Optimally we would merge them. I have some thoughts on how to do this and can work on this if no one gets to it first.

cc @rshriram @htuch

Contributor guide

Research direction
Review the existing PR #4873 and understand the differences between filter state and dynamic metadata. Then propose either clear documentation or a plan to merge them.
Tech stack
cpp
Domain
backend
Issue type
Documentation
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Envoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30