`tt cluster publish` usage is confusing and dangerous
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
It is unclear from cluster publish <app> <new.yaml> command name that it replaces a config.yaml in the application directory. Need more details in the help.
This command does not ask for confirmation, and a user may accidentally overwrite existing configuration (expecting ETCD pubishing, for example)
This command replaces existing configuration, but only if it is valid app configuation. Or even if the config valid, but unavailable: etcd is stopped, for example. This command should not require valid application to replace its config.
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 at the tt cluster publish <app> <new.yaml> command and inspect its help text and publish flow. Reproduce replacement with an existing config.yaml, including when etcd or the application configuration is unavailable. Done means the help clearly warns about replacement, accidental overwrites require confirmation, and replacement does not depend on a valid or available application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100