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
So I am trying to figure out how to avoid bootstrapping the nodes when using machine/machine_batch resource. I want it to create EC2 instances, check for the 'Windows is ready' message from AWS and then gracefully end. I tried using options:
[1]
[1] option creates the EC2 instance and then exits without waiting for 'Windows is ready' message from AWS.
[2] option creates the EC2 instance and then waits for 'Windows is ready' message but then also tries to connect to the instance (which I don't want it to do).
From the definition in Chef docs here, I believe action :ready should do what I want but it doesn't do it. Any other option or combination that I should use apart from the above? Or is there any way to accomplish what I want here?
The overall idea is to not allow WinRM connection from provisioner node to the provisioned node which happens as part of machine convergence and then use AMIs with pre installed and configured chef-client.
Please let me know if more clarification or information is needed.
Thanks!
The text was updated successfully, but these errors were encountered:
Ohai,
So I am trying to figure out how to avoid bootstrapping the nodes when using
machine/machine_batch
resource. I want it to create EC2 instances, check for the 'Windows is ready' message from AWS and then gracefully end. I tried using options:[1]
[2]
[1] option creates the EC2 instance and then exits without waiting for 'Windows is ready' message from AWS.
[2] option creates the EC2 instance and then waits for 'Windows is ready' message but then also tries to connect to the instance (which I don't want it to do).
From the definition in Chef docs here, I believe
action :ready
should do what I want but it doesn't do it. Any other option or combination that I should use apart from the above? Or is there any way to accomplish what I want here?The overall idea is to not allow WinRM connection from provisioner node to the provisioned node which happens as part of machine convergence and then use AMIs with pre installed and configured
chef-client
.Please let me know if more clarification or information is needed.
Thanks!
The text was updated successfully, but these errors were encountered: