## New Features - Groundwork: We added some initial back-end and API support for Chef InSpec Waivers with more work to continue in the new year. ## Improvements - Level Up: Chef Automate now uses Habitat 0.90.6, ElasticSearch 6.8.3, and OpenJDK 11. - Whack-a-mole: We resolved a few vulnerabilities that popped up from our periodic `npm audit`. (No actual moles were harmed.) - No Dawdling: Purges will now fail if each step of the purge does not happen within 10 minutes of scheduled execution. - Bite-sized: Compliance profiles now have server-side filtering and pagination! To maintain backward compatibility, only requests with the `per_page` parameter set to a non-default value, other than zero, will be paginated. - All the Metadata!: Client Run and Compliance Node detail views now display more metadata. - What's Up, Doc?: The [API docs](https://automate.chef.io/docs/api/) feature a new section on our authentication header format, which follows the OpenAPI specifications for security definition objects. ## Bug Fixes - Desensitized: The system now tolerates the final virgule in file paths, such as `/path/to/backupid/`. Previously, when passing a file path for backup purposes, only file paths with the last `/` removed would work, such as `/path/to/backupid`. - Rock On: We changed our configuration to avoid a low `DefaultMaxTasks` constraint for users on SUSE Linux Enterprise Server (SLES). Chef Automate failures with the error message "fork rejected by pids controller" should no longer appear. - Restored: Input styles on a random assortment of input fields resumed their normal, happy, and uniform styles after recent layout updates. - Working...: Menus in the top navigation no longer display behind the progress spinner overlay. - Permanent Marker: Users may no longer edit the name or tags on ingested nodes, or nodes with no manager, but other ingested nodes fields may be edited. - Noted: Clean up of the scanning functionality ensures that errors, when they exist, are always reported. ## Beta Features ### Applications - API It Up: The output of Habitat health checks is now exposed via the Applications APIs. - Expected Behavior: Selecting a health status filter with zero services in the _Service Group_ Details sidebar no longer causes a new service group to be selected. - Steady: Selecting a new health status filter on the _Service Group_ table will only change the _Service Group_ Details sidebar if the new health status filter results do not include the currently selected Service Group. - Reversed: The _Service Groups_ display used to switch current and previous health statuses when generating messages about health status changes, but we fixed this. - Keep It Simple: Note a small performance improvement by avoiding a double fetch of data. ### Identity and Access Management v2 - Speedy: Experience a substantially faster loading of the _Projects List_ page, since we removed a network call per project. - Re-ordered: The percentage done display now progresses correctly after selecting the _Update Projects_ button. Previously, the percentage done display would sometimes start at 100% and then quickly reset due to a minor race condition. - Stand Still: The _Global Project Filter_ no longer auto-refreshes its project list while you select your project(s). Previously, users lost their selection due to the periodic auto-refresh of the displayed project list.