Idea: `tt` support Tarantool 3.* apps without `instances.yml`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
Currently, tt always requires a instances.yml file for multi-instance applications. This is fine for cartridge-based apps, but it can be inconvenient for Tarantool 3.x apps development. A Tarantool 3.x app already has a centralized configuration that contains a list of available instances, and all these instances should be listed in the instances.yml file. The idea is to use all the instances listed in the configuration, even if the instances.yml file is missing. If the user runs tt start, and there are too many instances in the config, tt will prompt for confirmation. During application distribution, the instances.yml could be generated to specify which instances to run.
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 the tt start entry point and the current handling of instances.yml, then inspect how Tarantool 3.x application configuration lists instances. Define how missing instances.yml, confirmation for many instances, and distribution-time generation should work; the issue is done when this behavior is specified and implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100