show bounded source name for DM-worker in `tiup dm display`
Nobody has claimed this yet.
- 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:
If the user deployed large amounts of DM-worker instances and lots of them have bounded with upstream sources. the user may need to know the bound relationship between DM-worker instances and upstream sources with TiUP.
Describe the feature you'd like:
show bounded source name for DM-worker in tiup dm display
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 by tracing the tiup dm display command and how it gathers DM-worker information. Identify where the worker-to-upstream binding is available, then verify that the bounded source name appears in the display output for workers with upstream sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100