pingcap / pingcap/tiup

Be able to run commands without network access

Open
#123 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

difficulty/medium help wanted type/enhancement
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

For CI and other automation, it is nice to be able to run commands and be able to guarantee they will not use the network. This implies nothing should be updated (local repositories are a grey area).

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

The issue names no files, tests, or entry points. Start by locating the command execution path and any update or network-access behavior, then clarify which commands and local repository operations are in scope. Done means CI can enforce that selected commands perform no network access or updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.