Improve the usablity of `tiup cluster import` subcommand.
Open
Nobody has claimed this yet.
ansible
status/TODO
type/feature-request
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
- Supplement the exporters when import a cluster from ansible.
- Migrate exporters to the unify directory when import a cluster from ansible.
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 at the tiup cluster import subcommand and trace its Ansible cluster import flow, focusing on how exporters are handled. Clarify the expected exporter supplementation and the target unify directory before implementing. Done means imported Ansible clusters include the needed exporters and place them in the unify directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100