We are delighted to announce the availability of version 20190605190944 of Chef Automate 2.
ICYMI: If you are upgrading from a version prior to 20190410001346, please read our Important Compliance Outage Announcement.
- New API support: Upon ingestion of a report from Chef Infra or Chef InSpec, metadata information about the node and status of the report will be sent to the
nodesAPI. Make API calls to the
api/v0/nodes/searchendpoint to find out which of your nodes passed their penultimate scan and failed the most recent one. The same can be done for the ccr status, and filters can be combined. See the Nodes API documentation for more information and examples.
- The Feature Formerly Known As: The Asset Store page is now known as the Profiles page in Automate and its documentation.
- Change of Address: The following pages and their paths now appear under the expanded Compliance tab in the top navigation bar:
- Reports - compliance/reports
- Scan Jobs - compliance/scan-jobs
- Profiles - compliance/compliance-profiles
- Bam!: New nodes can now be added directly from Node Integration page under the Settings tab.
- Search Expansion: New fields were added to the Compliance Report search:
- Chef tags
- Policy group
- Policy name
- No More Magnifying Glass: The Event Feed page features larger text sizes for better readability.
- Customize Notifications: Specify to only send ServiceNow InSpec scan failure notifications for critical control failures.
- Search Multiplier: Filter nodes for a scan job using multiple tag key/value selections.
- Error Feedback: If a report is too large to be ingested, the scan job will now fail and send an error message.
- Narrow Down: Suggestions that appear in the Client Runs search bar are filtered to only show values from the nodes currently visible on the page.
- Name Tags Not Required: Nodes added without a name via cloud integrations will now use their ids instead.
- Replaced Filter: Wildcard filters of the same type in the Client Runs search bar are now treated as 'OR' filters.
- Keep It Simple: Compliance will now use one ElasticSearch connection per compliance-service instance. By reducing the number of sockets being managed, this solves a problem of receiving
could not get elastic connectionerrors in Compliance.
- In Order: Search bar types under the Client Runs page are now sorted alphabetically.
How to Upgrade
By default Chef Automate 2 will automatically upgrade to this new version. If you have disabled automatic upgrades you can manually initiate an upgrade by running:
chef-automate upgrade run
As always, we welcome your feedback and invite you to contact us directly or share your feedback online. Thanks for using Chef Automate 2!