News from chef.io
Your guide for the easiest way to get all of your Chef data moved over to new Chef infrastructure with the least impact to your users.
See how to migrate to the cloud with Chef Automate and AWS. Start your cloud journey with confidence.
SAP adopted Chef to automate the deployment of their on demand developer landscapes, resulting in decreased complexity for developers and increased speed of deployment.
In our last blog post, we gave you an introduction and high-level overview of how Chef Automate and HPE OneView work together to enable cloud-like speed on bare metal hardware. In this post, we'll explore a bit deeper with technical details and code examples. There are the three main requirements...
Previously, you could manually install Chef InSpec in order to run compliance-as-code solutions through Chef. Now, OpsWorks for Chef Automate supports integrated and continuous compliance, and you can view the results in a unified dashboard through compliance views in Chef's UI.
Not quite a year after launching Chef Automate, cloud-based software development company Chef has improved support for InSpec and Habitat - its code testing and app building projects - within its flagship product as it kicks off ChefCon 2017.
Take advantage of live demos, Q&A with Chef experts, and hands-on tutorials to help you prepare for Chef 14 and Chef 12 end-of-life.
At Chef, we understand that Infrastructure Automation enables your business to succeed, but it isn't the reason your business exists. Ultimately, all software is a careful balancing act of introducing new features, fixing bugs, and saying no to ideas that we might love to do but are too...
The February release of Chef Automate marks the GA release of the compliance scanner with job scheduling, and adds features to make analysis easier, such as date-range search.
A new feature that has been merged into the upstream kitchen-vra driver. You now have the ability to use the Catalog Names instead of the Catalog IDs for your instances.