tiup cluster import should read deploy_dir and port for monitored_servers section
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
From https://asktug.com/t/topic/69507
TiUP doesn't support deploy the cluster with different monitored_servers config, so it only read [all:vars] at this time.
Some times the user may config the port or deploy dir into every instance and keep them same (every instance has same deploy dir and port), in this case, we should deal with it correctly (put it into global), only if we find two different deploy dir or port, reports error.
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
Start from the TiUP cluster import handling for the monitored_servers section and compare it with the current [all:vars] parsing. The change is done when identical deploy_dir and port values across instances are promoted to the global configuration, while differing values produce an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100