I’m about to release chef-provisioning version 1.2.0 with the following changelog:
Updating for newly introduced Socketless mode. If the local chef-zero url is
chefzero://... then we replace it with
http://... on the target VM #337 https://github.com/chef/chef-provisioning/pull/337
Bumped winrm dependency to 1.3.0 #332 https://github.com/chef/chef-provisioning/pull/332
I will also release chef-provisioning-aws 1.2.0 with the following changelog:
Security groups can be referenced by group-name, don’t need a data bag entry (#194 https://github.com/chef/chef-provisioning-aws/pull/194)
Added support for tags across almost all resources. See the README for examples (#190 https://github.com/chef/chef-provisioning-aws/pull/190)
aws_route_table with the ability to ignore routes with regex matching. This supports AWS performing automatic route switching for HA purposes without chef-provisioning interfering with that logic. (#172 https://github.com/chef/chef-provisioning-aws/pull/172)
aws_route_table to propogate routes from provided virtual gateways. See the comments in the resource for specifics. (#151 https://github.com/chef/chef-provisioning-aws/pull/151)
docs/examples/ref_* examples to execute correctly and fixed broken integration tests
Thanks to everyone for their contributions!
A final NOTE: these gems will not work with the current version of the ChefDK. If you
chef gem install chef-provisioning -v 1.2.0 then you’re gonna have a bad time. There is a conflict between chef-provisioning 1.2 and knife-windows 0.8.x where they want different versions of winrm. This will be resolved with the next ChefDK release, which will include chef-provisioning 1.2, knife-windows 1.0 and winrm 1.3. To take advantage of the new gems you can use a Gemfile in your cookbook and
bundle exec your runs, or you can wait until the next ChefDK release is out.