tt CLI (2.7): `tt logrotate` don't exit at non-running instance
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: tt CLI
Since: tt 2.7.0
Dev ticket:
Root document: https://www.tarantool.io/en/doc/latest/reference/tooling/tt_cli/logrotate/
SME: @ AlexandrLitkevich @ oleg-jukovec
Details
Just warn and proceed with the other instances, like tt stop and
tt kill do.
Requested by @elhimov in https://github.com/tarantool/tt/commit/4ed4103123233cb4c37ac8872821a4a2ada1d87c.
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 with the root document at https://www.tarantool.io/en/doc/latest/reference/tooling/tt_cli/logrotate/ and compare the documented behavior of tt logrotate with tt stop and tt kill. Done means a non-running instance produces a warning while processing continues for other instances.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100