Connect doesn't default if only one instance available about multipass HOT 4 CLOSED

We've discussed this and are generally in favour, only question is what to do when there are more than one instances and you issue multipass connect - do we interactively ask you which one to connect to, or error out?

from multipass.

Also, tab completion should fill out the only vm automatically, so multipass connect <tab><tab> should automatically fill that in.

Also, if there are more than one instances defined, connect only tab completes running instances.

from multipass.

multipass connect is now multipass shell.
I needed to look in code to realize that.

We've discussed this and are generally in favour, only question is what to do when there are more than one instances and you issue multipass connect - do we interactively ask you which one to connect to, or error out?

Is this enhancement still desired?
Changing behavior multipass connect if only one, none or more than one instance is running could be confusing.
Should similar behavior be implemented for other commands e.g. multipass stop ?

If it's still desired feature I think that in case there are more instances running command should list running instances.

Also, tab completion should fill out the only vm automatically, so multipass connect <tab><tab> should automatically fill that in.

That's interesting solution without changing behavior of multipass shell command.

from multipass.

Yeah I'm gonna close this now. We're working to design a related solution, will keep you posted.

from multipass.