pingcap / pingcap/tiup

Could tiup supports `http_proxy` env param?

Open
#1,936 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/feature-request
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Feature Request

Is your feature request related to a problem? Please describe:
For https://github.com/pingcap/tiup/issues/1437, I think the root case is http_proxy and https_proxy env params are not be used.

Describe the feature you'd like:
Let telemetry supports use http_proxy env param

Why the featue is needed:
tiup quit so slow even just use tiup playground --help

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the telemetry network requests triggered by tiup playground --help and checking how proxy environment variables are handled. Done means telemetry honors the requested http_proxy and https_proxy settings and the command no longer waits unnecessarily when telemetry cannot connect.

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
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.