-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
awless stop instance ID returns an error message #99
Comments
This is normal, as you should write However, typing |
In the meantime (while we think of a good approach for that - several come to mind), here is something that can help. Having the following bash functions in one's env ( function startinstance() {
awless start instance id="$1" -f
}
function stopinstance() {
awless stop instance id="$1" -f
}
function delinstance() {
awless delete instance id="$1"
} ... and completion comes for free! The So a typical use would be: $ stopinstance @my-instance-name # referring instance by name using the alias notation
or
$ startinstance id-2352p52j452 |
Oh, my bad.
I'm ok with that, so maybe add a more valuable error message like:
|
Ok I know why I typed the wrong command: |
Good point. Thanks for your feedback, we are going to search a better approach for this and at least improve error messages. |
Yes, that's my favorite awless typo too! Building on what you suggest, we can catch both
|
Hi,
It common to write the instance ID in the CLI, but awless returns a error message:
It would be cool to use the ID for starting / stopping / whatever the instance.
The text was updated successfully, but these errors were encountered: