You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there is a reason for commands (eg. node create/terminate) to be synchronous + why they do things in order rather by doing things at the same time?
For example when creating nodes, lets say 3 so the parameter for create is --count 3. They SHOULD be launched at the same time in AWS but now I have to wait for them to be created one by one. Im impatient, I don't want to wait ;)
Same goes for terminating the node(s). There should be at least unattended option because usually I don't care how is the termination progressing. I just want to delete the nodes and preferably put multiple nodes so I don't need to repeat the command three times if I have three nodes to terminate.
Feature introduced in 1.5.0 Process Multiple Items In One Command would ease the pain and would be nice to have also in this aws plugin but that should be in it's own issue?
EDIT: after thinking this a little more, maybe its the synchronous nature of the ruby? :) I use nodejs/javascript as my main language nowdays so parallelism/async comes naturally to me and I did not remember this.
The text was updated successfully, but these errors were encountered:
Hi,
I was wondering if there is a reason for commands (eg. node create/terminate) to be synchronous + why they do things in order rather by doing things at the same time?
For example when creating nodes, lets say 3 so the parameter for create is --count 3. They SHOULD be launched at the same time in AWS but now I have to wait for them to be created one by one. Im impatient, I don't want to wait ;)
Same goes for terminating the node(s). There should be at least unattended option because usually I don't care how is the termination progressing. I just want to delete the nodes and preferably put multiple nodes so I don't need to repeat the command three times if I have three nodes to terminate.
Feature introduced in 1.5.0 Process Multiple Items In One Command would ease the pain and would be nice to have also in this aws plugin but that should be in it's own issue?
EDIT: after thinking this a little more, maybe its the synchronous nature of the ruby? :) I use nodejs/javascript as my main language nowdays so parallelism/async comes naturally to me and I did not remember this.
The text was updated successfully, but these errors were encountered: