[chef] Re: Re: Chef 12.5 and ChefDK 0.9 release candidates available!

[John Keiser < >]

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 < " target="_blank"> > wrote:

Congratulations!

Any chance we can name resources explicitly rather than being tied to <cookbook>_<filename>? Like ‘provides :foo’?

Thanks,

Jos

From: John Keiser
Reply-To: " " target="_blank"> "
Date: Thursday, October 1, 2015 at 11:44 AM
To: " " target="_blank"> "
Subject: [chef] Chef 12.5 and ChefDK 0.9 release candidates available!

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