Chef Automate Release 1.8.3

Chef Release Announcements
1

We are delighted to announce release 1.8.3 of Chef Automate. The release is available for download from https://downloads.chef.io/automate.

New Features

Compliance Scanner and Job Scheduling now GA!

This month’s release extends your ability to assess and control the state of your system. While we’ve kept our core functionality, we’ve expanded your ability to see your entire system with compliance scans of any node–even those not managed by Chef. What’s more, while you can still run compliance scans on a one-time, ad-hoc basis, you can also use the Job Scheduling feature to run your compliance scans on a recurring basis.

For more information on using these features, check out the documentation here: https://docs.chef.io/automate_compliance_scanner.html

Compliance Search Date-Range Support

The search bar in compliance now has a date range picker, allowing you to control the starting and ending dates for display.

Additional Features

  • The node’s platform version is now displayed in Compliance node lists
  • LDAP authentication now supports simple_tls encryption

Resolved Issues

  • Node scan history page now obeys profile filter set on compliance dashboard
  • Removed the sudo credentials option when creating or editing a node
  • Fixed a race condition preventing the ‘updates available’ notification for Compliance profiles from being displayed
  • Correctly displays platform versions in the Compliance nodes list
  • Fixed missing input validation on Compliance UI
  • Rubygems installed into Automate with an overly restrictive umask are now fixed when automate-ctl reconfigure is run
  • Passwords and keys fields no longer display values when editing a credential
  • The Compliance UI now displays a spinner when loading pages
  • Scan jobs are now nested inside their parent job
  • The date picker on the Compliance Reporting page now considers the ‘end of day’ in UTC
  • The Compliance ‘Failed Nodes’ icon now matches the node failure icon
  • The Elasticsearch timeout during an automate-ctl reconfigure has been increased to 60 seconds
  • Stale Elasticsearch lock files can be cleaned after a crash with automate-ctl delete-elasticsearch-lock --stale-lock-only
  • Fixed CA certificate path location on SuSE
  • The data collector API now returns a 503 when Automate is in maintenance mode
  • The Elasticsearch API now returns 400 if sent a HTML script tag to prevent XSS attacks

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!