Latest Stories
Top 10 Most Viewed Blogs of 2016
In 2016, we published more than 200 blog posts, highlighting major releases and announcements, partnerships and integrations, skill-building and how to articles, and more. Here are the top ten most viewed posts of 2016.
Test Kitchen: Driver caching mechanism
I’m happy to announce a new driver caching mechanism for Test Kitchen. You can use it with provisioners to cache downloads and other files between provisions. For people who use the kitchen-vagrant driver to run Chef, we’ve introduced local caching of the chef-client packages.
Why Habitat? The Habitat Supervisor and its Environment
This is the fourth post in our series, Why Habitat? You can catch up with Part 1, Part 2, and Part 3. In our last post, we began covering the Habitat supervisor. We explored how it allows you to manage the runtime life cycle of your application.
Automating compliance for financial services
We’ve been talking about the importance of incorporating compliance into your development workflow for a while now. With Chef Automate, we’ve delivered an enterprise-grade solution for turning compliance policy into code.
VMware vRA 7.0+ and Chef
We’re happy to announce that Chef can now drive VMware’s vRA 7.0+ automation suite. We’ve released 2.0.0 versions of both knife-vrealize and kitchen-vra along with a 1.0.0 version of chef-provisioning-vra.
Current state clarity, Part 2 – Policyfiles
If you’ve never heard of Policyfiles, you should start by reading Michael Hedgpeth’s excellent Introduction to Policyfiles.
Policyfiles, Push Jobs, and Provisioning – Clarity on the current state of the Chef ecosystem
The 2016 Chef Community Summit in Seattle brought to light a particular set of concern and confusion in our community around the future of three Chef ecosystem tools: Policyfiles, Push Jobs, and Chef Provisioning.
Chef at AWS re:Invent 2016
AWS re:Invent is an exciting event, jam packed with announcements. This year was no exception. Chef was excited to be among the 32,000+ AWS cloud customers and partners in attendance. Leave it to AWS to be able to hide an 18-wheeler truck and drive it on stage during a keynote.
Why Habitat? The Supervisor and Run Lifecyle
This is the third post in our series, Why Habitat? You can catch up with Part 1 and Part 2. In our previous posts, we talked about packaging your applications and compared results between packaging using a Dockerfile vs using Habitat. The core of Habitat packaging is the plan.
