Adds guards to cluster deletion.
- If cluster has running apps -> throw an error
- If cluster has stopped apps -> confirm w/ user that apps and logs will be deleted
* drop name column from cluster list
* change create cluster to accept id as well
* rename validator
* remove cluster name from logs
* fix merge with master
* more merge with master issues
Cluster creation and deletion can take a long time. Instead of having these long running operations happen in the background, they should happen in the foreground. The advantage is that failures are brought to the users attention immediately, instead of the next time they decide to run `lightning list clusters`.
While the CLI waits for the cluster to run / delete, it will display cluster status changes to the user.
This PR also hides the `--enable-performance` and `--edit-before-creation` creation flags, as well as the `--force` deletion flag. They are either not frequently used (performance mode is expensive), or prone to misuse.
Co-authored-by: Neven Miculinic <neven.miculinic@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Raphael Randschau <nicolai86@users.noreply.github.com>
## What does this PR do?
Removes the ability to specify `--instance-types` when creating clusters.
Instead, all clusters will be able to use every instance type supported by the platform.