Chef Automate Release 1.6.179

We are delighted to announce release 1.6.179 of Chef Automate. The release is available for download from

New Features

The beta period is complete and this feature is now generally available and enabled by default. Chef Automate supports simple configuration of Slack or webhook notifications for Chef client run failures and critical compliance control failures.

Authentication for External Elasticsearch
Communication between Chef Automate and externally managed Elasticsearch clusters can now be configured to use SSL. Additionally we have added support for authentication via Elasticsearch X-Pack for external clusters.

Resolved Issues

  • Redesigned the CSV and JSON export for compliance data; it is now served from an API endpoint and can be used separate from the UI. Previously the export omitted some records; it now includes all data, and accordingly the report may take more time to generate.
  • Fixed an issue where upgrading Elasticsearch 5.x (during upgrade to Chef Automate 1.6.x) fails if there are incompatible configuration options for Elasticsearch 2.x specified in delivery.rb
  • Resolved an issue where automate-ctl delete-node was not removing nodes from the compliance UI
  • Corrected a regression with the mark-nodes-missing script; nodes will now be set to missing if they have not checked in for 12 hours
  • Upgraded Ruby to version 2.4.2 to address multiple CVEs

We encourage you to upgrade often. As always, we welcome your feedback and invite you to contact us directly or share your feedback online. Thanks for using Chef Automate!