reorganize tiup cluster fail logs
Open
Nobody has claimed this yet.
help wanted
type/enhancement
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
When tiup cluster fails, a log will be generated in working directory. This can make the fail logs everywhere and won't be easy to find again when user changes their working directory.
I suggest to put the log inside home directory like ~/.tiup/cluster/cluster_name/fail-date.log. Or just write to stderr when provided -vv option.
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
No files, tests, or entry points are named. Trace how tiup cluster writes failure logs, then resolve whether logs should move under ~/.tiup/cluster/cluster_name or be emitted to stderr with -vv; done means failures no longer leave logs in the working directory.
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