envoyproxy/envoy

Track original config resources in SDS

Open

#9,670 opened on Jan 13, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/xdshelp wantedtech debt

Repository metrics

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

Description

Currently SDS stores various pieces of the original config, e.g. TLS certificates, as distinct objects. This makes assembling a config dump challenging, in particular when we have cross v2/v3 versioning concerns. We should probably switch to just storing the SDS resource that was delivered on the wire (with redaction).

Contributor guide

Research direction
Inspect how SDS currently stores config resources and understand the config dump assembly process. Consider how to store the original SDS resource with redaction.
Tech stack
cpp
Domain
backend
Issue type
Refactor
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
C++Envoy basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60