envoyproxy/envoy

More flexibility in choosing static vs dynamic config in integration tests

Open

#6,327 opened on Mar 20, 2019

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
enhancementhelp wantedtech debt

Repository metrics

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

Description

In discussion on #6214, @alyssawilk outlined a nice redesign of the integration testing framework's interaction with configs. Here are the relevant comments:

I'm hoping by end of year the integration test framework will just let you live load any component as we can in prod

I'd like to have config booleans for static vs dynamic for all the DSes. So if they were all false, we'd get what we have today, and if they were all true we'd have what is described above, and whatever section is true has the hard-coded configuration swapped out for the discovery service config.

This issue will track that work.

Contributor guide

Research direction
Examine the proposed booleans for static vs dynamic config in integration tests and implement the change for one discovery service as a proof of concept.
Tech stack
cpp
Domain
backend
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.
Mostly clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20