Christine Draper

@maggiolo00 - Yes

@maggiolo00 That would be very useful, thanks! Would you be able to publish it to Maven, too?

Is it possible that TCP forwarding is disabled on your SLES VM?

I'd also suggest downgrading to chef 12.3, as there are some known compatibility problems between chef provisioning and chef 12.4.0 which you might otherwise encounter (https://github.com/chef/chef-provisioning/issues/377)

I'm still seeing the behavior where it tries to regenerate the image. Let me know if there's any info I can get to help debug.

Here's some more details. What I actually did was: 1) Run recipe to create machine_image with AMI Name "appserver_image" 2) Delete chef data (i.e. data bag machine_image/appserver_image.json) 3) Rerun recipe...

Is there a way to tell which resources are using V2 API vs V1? I just got caught out because aws_autoscaling_group is still on V1...

That counts as 'a way to tell'. Thanks!

It's possible this only happens in the following case: 1) Create machine_image (which happens to be used in autoscaling group) 2) Destroy machine_image and autoscaling group 3) Recreate machine_image (i.e....

Tested with chef-provisioning 1.2.0. It is still occurring. I tried: ``` machine "test" do run_list ["apt"] end ``` and each run, it converges test with: ``` - update node i-5b573cac...