Hey everyone!
We’d like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new
Read up on the features and download here:
Chef 12.5 and its companion, ChefDK 0.9 are imminent, and we need your help! Please install the nightlies (see below) and try out some of the new features (also below) and let us know if there are issues! These prereleases will be up to date with the...
Here’s what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new
We’ve already gone through a ton of testing with this release, but we can’t
Thanks!
–John
Looks like there might be a little syntax error on the "snazzy new resource
On Thu, Oct 1, 2015 at 11:44 AM, John Keiser jkeiser@chef.io wrote:
Hey everyone!
We'd like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new
Read up on the features and download here:https://www.chef.io/blog/chef-12-5-and-chefdk-0-9-prerelease-announcement/
Here's what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new
We've already gone through a ton of testing with this release, but we
Thanks!
--John
JosB
October 1, 2015, 7:07pm
3
Congratulations!
Any chance we can name resources explicitly rather than being tied to _? Like ‘provides :foo’?
Thanks,
From: John Keiser"chef@lists.opscode.com mailto:chef@lists.opscode.com ""chef@lists.opscode.com mailto:chef@lists.opscode.com "
Hey everyone!
We’d like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new features, and we’d like to get some feedback on them before we go live.
Read up on the features and download here: https://www.chef.io/blog/chef-12-5-and-chefdk-0-9-prerelease-announcement/
Here’s what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new release works for you!
We’ve already gone through a ton of testing with this release, but we can’t make it great without you
Thanks!
–John
You can use "provides" or "resource_name" for that. Just put "resource_name
On Thu, Oct 1, 2015 at 12:07 PM, Jos Backus josb@mobileiron.com wrote:
Congratulations!
Any chance we can name resources explicitly rather than being tied to
Thanks,
From: John Keiserchef@lists.opscode.com "chef@lists.opscode.com "
Hey everyone!
We'd like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new
Read up on the features and download here:https://www.chef.io/blog/chef-12-5-and-chefdk-0-9-prerelease-announcement/
Here's what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new
We've already gone through a ton of testing with this release, but we
Thanks!
--John
Fixed, thanks!
On Thu, Oct 1, 2015 at 11:54 AM, Greg Barker fletch@fletchowns.net wrote:
Looks like there might be a little syntax error on the "snazzy new
On Thu, Oct 1, 2015 at 11:44 AM, John Keiser jkeiser@chef.io wrote:
Hey everyone!
We'd like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new
Read up on the features and download here:https://www.chef.io/blog/chef-12-5-and-chefdk-0-9-prerelease-announcement/
Here's what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new
We've already gone through a ton of testing with this release, but we
Thanks!
--John
JosB
October 1, 2015, 7:26pm
6
Perfect, thanks John! I’m glad a cleaned up custom resource implementation made it into core Chef.
Cheers,
From: John Keiser"chef@lists.opscode.com mailto:chef@lists.opscode.com ""chef@lists.opscode.com mailto:chef@lists.opscode.com "
You can use “provides” or “resource_name” for that. Just put “resource_name :foo” (if you want to see “foo” in all the output and make “cookbook_filename” not even work) or “provides :foo” (if you want your resource to be addressable by both “foo” and “cookbook_filename”).
On Thu, Oct 1, 2015 at 12:07 PM, Jos Backus <josb@mobileiron.com mailto:josb@mobileiron.com > wrote:
Any chance we can name resources explicitly rather than being tied to _? Like ‘provides :foo’?
Thanks,
From: John Keiser"chef@lists.opscode.com mailto:chef@lists.opscode.com ""chef@lists.opscode.com mailto:chef@lists.opscode.com "
Hey everyone!
We’d like to ship Chef 12.5 and ChefDK 0.9 soon with a slew of new features, and we’d like to get some feedback on them before we go live.
Read up on the features and download here: https://www.chef.io/blog/chef-12-5-and-chefdk-0-9-prerelease-announcement/
Here’s what you can do:
Try out the new policy and custom resource features on ChefDK 0.9!
Run the Chef 12.5 client against your cookbooks to make sure the new release works for you!
We’ve already gone through a ton of testing with this release, but we can’t make it great without you
Thanks!
–John
