Envoy Proxy: Graduate network-proxy backend selection to a first-class option
Open
Nobody has claimed this yet.
p2
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Goal
Promote backend selection from the experimental TOOLHIVE_NETWORK_PROXY env var to a first-class, discoverable option.
Tasks
- Add a
RunConfigfield for the network-proxy backend. - Add a CLI flag (e.g.
--network-proxy) onthv run, wired through to the runtime. - Regenerate CLI docs (
task docs). - Decide whether the env var remains as an override or is retired.
Notes
Per the team convention that feature-flag/CLI exposure lands after a capability has stabilized behind an env var. Keep the default as Squid until #5900 decides otherwise.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the existing TOOLHIVE_NETWORK_PROXY handling into RunConfig and the thv run runtime path, then inspect the CLI definition and task docs workflow. Done means the backend is exposed through the new option, CLI documentation is regenerated, and the env-var behavior is resolved while Squid remains the default pending #5900.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100