ChefDK 0.1.0 Released

Chef Infra (archive)
1

Hi Chefs,

ChefDK 0.1.0 is out with a few bug fixes and improvements based on your feedback since our first release at ChefConf.

Full details of the release are here: http://www.getchef.com/blog/2014/04/29/chefdk-0-1-0-released/

You can download it here: https://www.getchef.com/downloads/chef-dk/

Happy cooking,

–
Daniel DeLeo

2

Is there a way to upgrade chefdk in place? Also what happens to included
gems when I upgrade? i.e. kitchen-vagrant.

Regards,

Nic Grayson

On Tue, Apr 29, 2014 at 11:20 AM, Daniel DeLeo dan@kallistec.com wrote:

Hi Chefs,

ChefDK 0.1.0 is out with a few bug fixes and improvements based on your
feedback since our first release at ChefConf.

Full details of the release are here:
ChefDK 0.1.0 Released - Chef Blog | Chef

You can download it here: https://www.getchef.com/downloads/chef-dk/

Happy cooking,

--
Daniel DeLeo

3

Any ETA on when a Windows build will be available?

David

On Tue, Apr 29, 2014 at 9:20 AM, Daniel DeLeo dan@kallistec.com wrote:

Hi Chefs,

ChefDK 0.1.0 is out with a few bug fixes and improvements based on your
feedback since our first release at ChefConf.

Full details of the release are here:
ChefDK 0.1.0 Released - Chef Blog | Chef

You can download it here: https://www.getchef.com/downloads/chef-dk/

Happy cooking,

--
Daniel DeLeo

4

On Tuesday, April 29, 2014 at 9:22 AM, Nic Grayson wrote:

Is there a way to upgrade chefdk in place? Also what happens to included gems when I upgrade? i.e. kitchen-vagrant.

Regards,

Nic Grayson

You can just install the new package and things should work (please file a bug report if you find this not to be the case).

If you’ve switched to running ChefDK as your primary ruby environment for Chef development, please see GitHub - chef-boneyard/chef-dk: DEPRECATED: A streamlined development and deployment workflow for Chef Infra platform. as the change to user-mode gem installs for chef gem means that executables installed via chef gem will end up in your home directory now.

Thanks,

--
Daniel DeLeo

5

On Tuesday, April 29, 2014 at 9:26 AM, David F. Severski wrote:

Any ETA on when a Windows build will be available?

David

We’re working on this right now. I’m pretty close to getting the actual software to build on a VM, but we also need to add windows machines to the build cluster, update the MSI packaging code (what we do for chef-client right now is a bit of a hack and not extensible), possibly deal with automated test issues (won’t know about that until we get a working build), and do some manual verification (which could also find new bugs to fix).

Tl;dr, we don’t have an exact date, but it’s being actively worked on.

--
Daniel DeLeo

6

Love it! Great work guys.

Do you have a General Linux tarball ? Or even just how you build it?
I want to package this for ArchLinux, have the same setup as everyone else
for compliance.

–
Regards,
Alfredo Palhares

7

We build it using GitHub - chef-boneyard/omnibus-chef: Omnibus packaging for Chef using this cookbook to prepare the machine: GitHub - chef-boneyard/omnibus: Prepares a machine to be an Omnibus builder. ┬──┬◡ﾉ(° -°ﾉ) (mostly just build-essential).

We can’t just make a “general linux tarball” because the builds are tied to a particular version of libc that differs across distros.

--
Daniel DeLeo

On Wednesday, April 30, 2014 at 9:11 AM, Alfredo Palhares wrote:

Love it! Great work guys.

Do you have a General Linux tarball ? Or even just how you build it?
I want to package this for ArchLinux, have the same setup as everyone else
for compliance.

--
Regards,
Alfredo Palhares