Nordstrom turning over Chef-Vault ownership to Chef

This is a guest post from our friend Doug Ireton at Nordstrom, detailing key information about the transfer of ownership for Chef-Vault from the Nordstrom team to Chef.

What is chef-vault?

Chef-Vault is a tool to help engineers securely manage passwords, SSL certs, and other secrets in Chef Recipes. Originally developed by Nordstrom during a consulting engagement with Chef 2 1/2 years ago, it has been in production use at Nordstrom and other companies ever since. It currently ships in the ChefDK.

In order to ensure a healthy future for Chef-Vault, Nordstrom will be turning over ownership of the open source project to Chef. Chef has moved the chef-vault repo on GitHub to the Chef organization.

Why is Nordstrom turning over Chef-Vault?

Chef-Vault has grown bigger than Nordstrom and we want to make sure that it’s able to thrive and grow with the needs of the community. Over the last few months, we haven’t been able to give Chef-Vault the attention it deserves. We still use Chef-Vault every day and plan to continue contributing code to the project and are very thankful for each person who contributed code, issues, and docs over the last 2 1/2 years.

At the end of October, we approached Chef to see if they were willing to take over ownership of Chef-Vault. They accepted and will maintain Chef-Vault going forward.

What are Chef’s plans for Chef-Vault?

Chef is committed to ensuring that Chef-Vault remains a high quality component of the ChefDK. We’re incredibly grateful to Nordstrom for contributing a crucial piece of software to our community and will continue to support and maintain Chef-Vault in the future.

Posted in announcements, chefdk, community, customers, security

Chef Server 12.3.1 Release Announcement

Ohai Chefs,

We’re pleased to announce that today we’ve released Chef Server 12.3.1. This is a small patch release that addresses severely degraded performance for nodes fetching cookbooks when all cookbooks have the same version number. Additionally, Chef Server now applies the full set of API-level tests to nightly builds of Chef Zero to ensure that the two APIs stay in sync.

The release can be downloaded at

Posted in community, release

Chef Delivery: A Guided Tour

Chef Delivery accelerates the adoption of continuous delivery and encourages DevOps collaboration. It provides a proven, reproducible workflow for managing changes as they progress from a developer’s workstation, through a series of automated tests, and out into production.

In this recorded webinar (presented on November 17, 2015), Nathen Harvey and Michael Ducy introduce you to Chef Delivery. They show you how to submit changes to Delivery and how to use the UI to track them as they move through the different stages of the pipeline. They talk a bit about the kinds of tests you can run, show you our GitHub integration, and give you an overview of how to control what happens in the pipeline with build cookbooks.

Q&A from the live webinar, including questions we didn’t have time to answer live, can be viewed below.

Read more ›

Posted in Delivery, webinar

Static Analysis: Improving the quality and consistency of your cookbooks

Every time we make changes to our cookbooks we are introducing risk. We can stop making changes to reduce the risk OR we can adopt new practices, like linting and testing, to help us manage that risk.

Linting tools provide automated ways to ensure that the code we write adheres to conventions that ensure code uniformity, portability, and uses best practices. This ensures everyone on the team writes similarly structured source code. It helps weave the expectations into the development of the code, and encourages collaboration over time. Ensuring the uniformity of source code helps set the expectations for fellow project contributors.

In this recorded webinar (presented on November 4, 2015) we focus on using Foodcritic and Rubocop (@ 21:45 in the recording) – two linting tools packaged in the Chef Development Kit (ChefDK) that you can immediately start using to reduce the risk in the cookbooks you develop. Q&A from the live webinar, including questions we didn’t have time to answer live, can be viewed below.

  • Introduction to Foodcritic (@ 10:00 in the recording)
  • Introduction to Rubocop (@ 21:45 in the recording)
  • Demonstration of the Tools (@ 30:45 in the recording)

Read more ›

Posted in cookbooks, webinar

Chef Analytics 1.2.0 Release

Ohai Chefs,

We are pleased to announce that Chef Analytics 1.2.0 is now available and features not only a new and improved look, feel, and user experience, but also improved node management abilities.

The biggest changes in this release are the new Node Detail page and the ability to purge node data. In the new Node Detail page, you can now explore your node run history, filter nodes based on status, and more accurately search your node list.

In addition, now you have more control over your disk space in Postgres with our new command to destructively remove node ohai data.

As always, you can download new releases of Analytics from

Thank you for using Chef!

Posted in analytics, release Tagged with: ,

Guest Post: Chef Extension for Visual Studio Code

Stuart Preston is an incredibly valued member of the Chef community and has been a key contributor in making an awesome experience using Chef along with the Microsoft product line. Stuart’s most recent addition to the Chef ecosystem is an extension for Visual Studio Code for developing your Chef code. The extension adds the ability to continually lint your code using Rubocop and autocomplete many of the resources found in core Chef.

Note: This post originally appeared on

Announcing: Chef Extension for Visual Studio Code

At Microsoft’s Connect() conference today, Visual Studio Code now supports extensions and has been open-sourced!

Over the past couple of weeks I have been working hard behind the scenes to build a Chef Extension for Visual Studio Code to make cookbook development an awesome experience on Windows, OS X and Linux.

The extension currently supports:

Syntax/keyword highlighting – Visual Studio Code will now recognise and colourise Chef DSL (including Chef Provisioning DSL). You can select from a number of different colour themes also available on the Marketplace.

Rubocop linting – The quickest way to identify issues in your code is to use a linting tool like Rubocop to perform static code analysis as you go. The Chef extension is preconfigured to automatically run Rubocop against your whole repo every time you save.

Snippet support – The extension includes autocomplete code snippets for all resources built into the Chef Client.

Here’s a demo of some of the new capabilities:

If you are working with Chef and you haven’t used Visual Studio Code before, I recommend you try it out. Downloads are available for Windows, OS X and Linux from Once you have installed it you can download the Chef Extension directly from within the application’s Command Palette.

At Pendrica we are committed to open source, and making more awesome for the Chef community. We believe that Infrastructure developers using Chef should have the same rich feature set and extended user experience as our counterparts in application development. We hope you enjoy using the extension which is open-sourced on our GitHub page at

Happy Cheffing!

Posted in community

Pre-release Announcement : Native 64-bit Windows Chef Client

Ohai Chefs!

I’m happy to share some exciting news for our Windows users – we now have a native 64-bit Chef Client available for you to download and try out here.

This version of Chef Client includes a 64-bit version of Ruby, and addresses one of the key pain points that Windows users can encounter when running a 32-bit process on a 64-bit version of Windows : namely, having to deal with the file and registry redirection that Windows does under the covers, that can sometimes cause unexpected results or script failures.

(See this link for more information on Windows redirection behavior).

To illustrate the pitfalls with redirection in a bit more detail, let’s look at an example of a simple Chef recipe that creates a file in a directory under the Windows System32 folder. The code below uses an environment variable to construct the path of the folder (test_dir) to write to. Then it uses Chef’s built-in directory and file resources to define the desired state.

process_type = ENV['PROCESSOR_ARCHITECTURE'] == 'AMD64' ? '64-bit' : '32-bit'
system32_dir = ::File.join(ENV['SYSTEMROOT'], 'system32')
test_dir = ::File.join(system32_dir, 'cheftest')
test_file = ::File.join(test_dir, 'chef_architecture_file.txt')

directory test_dir do
    action :create

file test_file do
    content "Chef made me, I come from a #{process_type} process."

If the code above runs in a 32-bit process on a 64-bit platform, Windows redirection will kick in, and the file and directory will actually get created in the SysWOW64 folder instead, which is not the desired outcome. However, when this recipe is run with a native 64-bit client, redirection will not come into play, and things will work as expected.

One other advantage of having the 64-bit package is that now we can also mark the MSI as 64-bit. This adds more control and granularity with Windows technologies like Group Policy, WMI, etc that can check the MSI flag and take advantage of it as needed.

Finally, the installer has also been re-architected for performance, with a noticeably faster install experience.

Note that this is pre-release software, and while we are excited to get this out early to share with you, there are a couple of things to call out:

  • The MSI size is larger than the production chef-client – it weighs in at around 170MB. This is something we are working on and expect to resolve before a final release.
  • This is not intended for production deployment – please only use in a non-mission-critical environment.
  • Please report any issues to us on github

Thanks, and enjoy!

Posted in announcements, chef, community, release

Voting now open for the Chef Board of Governance (CBGB)

Ohai Chefs!

On October 13th 2015 we announced the Chef Board of Governance (CBGB). Thanks to all of you who have nominated candidates.

Today – with a slight delay for which we apologize (looks like the recent launch got the best of us) – we are opening the voting!

As a reminder the Chef Board of Governance (CBGB) will consist of up to 12 members.

  • (1) Project Lead: Adam Jacob
  • (4) Users/Contributors
  • (4) Corporate Contributors
  • (3) Lieutenants
You can find all the details about how the board will work in this RFC

At this point I’m asking for your help getting the best possible representation for this group.

Please take the time to vote today! Voting for all categories will start on November 13 and will close on November 30. Every community member is encouraged and welcome to vote.

Once voting is closed, we will contact all people elected in the hopes he or she will accept the duty. We will then announce the final CBGB on December 7th.

Love, Adam

Posted in announcements, awesome chefs, community

Chef Business Momentum Continues to Surge with Top 100 Ranking in Deloitte’s 2015 Technology Fast 500™

Ranked 51st Fastest Growing Company in North America with Revenue Growth of 1,822 Percent as Enterprises in Every Industry Adopt DevOps to Become Software-Driven

SEATTLE – November 13, 2015 – Chef, the leader in automation for DevOps, today announced it ranked 51 on Deloitte’s Technology Fast 500™, a ranking of the 500 fastest growing technology, media, telecommunications, life sciences, and energy tech companies in North America. Chef ranked 2nd overall in Washington state with revenue growing 1,822 percent from 2011 to 2014.

Barry Crist, Chef CEO, commented:

“This is a phenomenal time for Chef. Many of the largest and most innovative companies in the world are using Chef’s automation and workflow platform to increase their software delivery velocity, which in turn increases their innovation velocity. This shift to embrace New IT is happening across all industries and is fueling Chef’s continually high growth rates.”
Chef’s annual recurring revenue growth is accelerating as the company gets larger. More than half of the Fortune 50 use Chef and 80 percent of Chef’s revenue comes from enterprise businesses.

Read more ›

Posted in announcements, press releases

Chef Server 12.3.0 Release Announcement

Ohai Chefs!

I’m happy to announce that Chef Server 12.3.0 is now available for download on the Chef Server Downloads Page and via our Apt/RPM repositories. Here are some highlights from this release:

  • Node API change to include Policy support.
  • ElasticSearch and external Solr support.
  • Object updates can now be posted directly to the search index.
  • Analytics queue monitoring.
  • Security updates to solr4 oc-id, and postgresql.
  • Many closed issues. Read more ›
Posted in announcements, release