Skip to content
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

Question about synchronous nature of the commands #47

Open
cahva opened this issue Mar 28, 2018 · 0 comments
Open

Question about synchronous nature of the commands #47

cahva opened this issue Mar 28, 2018 · 0 comments

Comments

@cahva
Copy link

cahva commented Mar 28, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants