We are delighted to announce the availability of version 20190325233053 of Chef Automate 2.
- Work It!: Existing Workflow users have access to the Workflow dashboard and tools in Chef Automate.
- Switch It!: Toggle
chef-automate maintenance [on|off]to use the new load balancer maintenance configuration option. When in maintenance mode, the load balancer serves an HTTP 503 error page, which is helpful to some users (Lookin' at you, OWCA friends) keep their data safe during a maintenance window.
- Check It!: Rewrote controls in the CIS Windows Server 2012R2 V2.2.1 and STIG Windows 2016 compliance profiles, so they execute faster and with loads on the target system. Domain Controller instances with large numbers of users and groups should see improvement and particular benefits with these changes.
- Find It!: Find more with less using the improved matching options for designating credentials for nodes from cloud integrations. When specifying tag key/value matches for your node integration nodes, we now support wildcard matching for:
- suffix -
- prefix -
- contains -
- exact -
- suffix -
- Tag It!: We have removed the restriction that prevented users from adding node tags with
- Filter It!: We've added a prefix wildcard search (
foo*) for scan jobs for the Automate manager node names and AWS-EC2 integration tag value searches.
- Clean It!: We were a little too conservative in our package cleanup mode---cleaning up only the first in the list of candidate packages---now we will clean up the entire set of obsolete Automate-installed packages.
- Use It!: Node Integrations update fixed! You'll now use your most recent credentials after updating a node integration, rather than re-using the older credentials.
- Fail It!: Scan jobs without any nodes should fail noisily (instead of silently)!
- Log It!: CIS compliance profiles for Windows Server won't return a false negative for the EventLog Retention control when the registry setting on the target host is stored as the datatype
- Spell It!: Event feed incorrectly displayed "keies," but now displays "keys" when multiple client keys are updated.
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!