pingcap / pingcap/tiup

support label like ansible

Open
#327 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

from customer:

tiup 不能支持组件别名, 最好和ansible一样哈

[tikv_servers]
tikv1 ansible_host=x.x.x.x ansible_port=22

ansible-playbook stop.yml -l tikv1
现在 -N 没之前的 -l 好用

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 locating tiup's handling of the current -N option and its component or cluster target selection. Compare that behavior with the provided Ansible alias example; done means users can define or address a component alias and select it with an -l-like workflow.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.