envoyproxy/envoy

enable Wasm filter enable per route

Open

#26,440 opened on Mar 29, 2023

View on GitHub
 (20 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmenhancementhelp wanted

Repository metrics

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

Description

We have use cases for enabling WASM filters per route. Are there any technical challenges for not supporting this or is it that it has not been implemented because there was not a use case for it?

If it is latter, Can we add support for it?

Contributor guide

Research direction
Investigate how Envoy currently configures HTTP filters per route and propose a design to allow Wasm filter configuration per route, considering existing filter chain mechanisms and potential code changes.
Tech stack
None
Domain
backendapi
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++EnvoyWasm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50