Handle multiple VM name arguments #112
Merged
+1,538
−1,692
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for multiple VM arguments.
Commands
delete
edit
(passes each as an argument to$EDITOR
-- vim handles this nicely using buffers)publish
start
stop
Notes
CmdResult
type toutils/utils.go
in order to aggregate errors as we iterate through VMs. This way, one failed iteration won't cancel the remainder.alpine publish foo foo
will only publish once).VM already stopped
error fromqemu/ops.go:Stop()
to avoid weirdness. This now just fails silently/is idempotent.AutoCompleteVMNames()
is already ready for multiple VMs, works as intended.Additional note
During testing, I ran
launch
many times. One time, I got a really unfortunate VM name from the randomizer. So, I went through the dictionaries (adjectives.txt
andnouns.txt
) and manually cleaned them up. No guarantee that I did a perfect job, but it should help mitigate issues in the future. In summary:person
,girl
,boyfriend
, etc)error
,data
, etc)Closes #87
Closes #88
Closes #89
Closes #91