`tt cluster show --validate` fails before starting config validation
Open
Nobody has claimed this yet.
3sp
bug
teamE
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
If cluster config has incorrect format somewhere above the instances, tt cluster show --validate does not start validation, because it fails when trying to collect instances info. For example, use 'group' instead of 'groups' in config.yaml.
$ tt cluster show cluster_crud_app --validate
⨯ cluster_crud_app: can't find an application init file: an instance "router" not found
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
Reproduce the issue with tt cluster show cluster_crud_app --validate and the config.yaml example using group instead of groups. Trace the command's instance-info collection before config validation; done means validation starts and reports the configuration format error instead of failing on the missing router instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100