Add cfg tarantool parameter checking
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
Some tarantool configuration parameters should not be used when running tarantool with tt (e.g. demonizing tarantool, using PID files...) because this might make the application not work.
Needs to add a wrapper for box.cfg() to prevent this.
Contributor guide
No contributing guide indexed for this repository
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 how tt launches Tarantool applications and where box.cfg() is invoked or exposed. Review the existing handling of daemonizing and PID-file settings, then define the complete set of parameters that must be rejected or wrapped. Done means tt prevents incompatible configuration from making the application fail, with coverage for the identified parameters.
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