## New Features

- This release doesn't contain any new major features, but we've got a great list of improvements and six bug fixes.

## Improvements
- When your license is getting close to expiration (within 90 days) -- whether a full license or a trial license--a banner appears reminding you that you need to take action to get that puppy renewed! It provides quick links to contact us as well as to a spot where you can apply a license in the UI.
- Compliance reports sent via scan jobs now trigger notifications.
- Scan jobs can be filtered by status.
- Improved experience when installing an already installed profile.
- Applying config to a running system is now more reliable (thanks, scheduled HUP).
- Upon requesting or applying a license, instead of a quick "License successful" notification you get the full whiz-bang experience confirming your license is approved and applied, along with details such as your expiration date.
- When applying or requesting a license, you now get positive visual feedback showing that the system is energetically working on your behalf, by disabling the button you just pressed during processing as well as showing a busy-spinner that is sure to keep you entertained. (Apologies but sometimes Chef Automate just responds too rapidly to even have time to show that it was off doing something, so you might not see our nitfy spinner at all--sad but true!)
- On the Event Feed, updates to cookbooks now give you the name and version of the cookbook, instead of just the version (which wasn't all that helpful).
- Manual node creation now includes the option to add (any number of) tag key/value pairs, and those tags can be used as a search query when creating a scan job. This allows users to group manually added nodes to their preference, and easily run scan jobs on those groups.
- Profile events now show user in event feed if available.
- Improve behavior of Event Feed in the face of partial service availability.
- We now configure ElasticSearch to stop accepting writes when available free disk space on the system drops below 250MB. This protects the system as a whole and allows more graceful recovery.
- When you migrate from 1.x versions of Chef Automate, we're now able to bring along any notification rules you may have configured.
- The entire row of the Client Runs table is now clickable. Finding just the right spot to click was fun, but we know this is much better experience now.
- Cookbook name and version is displayed in the Event Feed for cookbook actions.
- We taught the deployment service where to store backups by default (`/var/opt/chef-automate/backups`). Now you don't have to configure a backup path for the system before taking backups, but you still can if you want to.
- Webhook notification now include `timestamp_utc` in the JSON payload.
- Many improvements to support for running Chef Automate in environments using proxied access to the internet.
- We added a global config entry for controlling the log level of the entire system. Some services require further enhancement to respect this setting, but the new config entry still allows you to control log level across much of the system.
- We love our legal team and they love it when you accept our terms of service and master license and service agreement before installing and using our commercial software. When you run `chef-automate deploy` you'll now be asked to accept TOS and MLSA. You can accept at the prompt by typing "y", "Y" and decline with "n". Since we know you may want to automate your installation, you can also accept in a non-interactive fashion by providing a new flag `--accept-terms-and-mlsa`.
- The `chef-automate status` command now includes service uptime and process ID. For those of you not yet familiar with Habitat, this enhancement lets you obtain more detailed status information without having to drop out of the `chef-automate` CLI experience.
- Our preflight check now verifies internet connectivity to the key services that are needed for a successful deploy.
- Speaking of our preflight check, we now also check the version of the `chef-automate` CLI. We'll let you know if you need to update. We also increased the minimum free disk space required to 5GB. Presently, a fresh install of Chef Automate installs 2.6GB into `/hab` and we now require 250MB of free space in order to enable writes for ElasticSearch. So we increased the minimum free disk space to make sure you have enough room to add some data to the system.
- Improve UI handling of 403 unauthorized errors in Admin/API Token view.
- We no longer print credentials on the console during initial deployment. When you deploy, we'll generate a secure random password that you can use to bootstrap access to Chef Automate's web UI and we'll record this for you in `automate-credentials.toml` which is written in the directory from which you invoked `chef-automate deploy`.
- We realized the `--admin-password` flag for the `deploy` and `upgrade-from-v1` subcommands wasn't quite safe for general consumption so we've taken the measure of hiding it for now (shhh). The issue is that the local-user-service validates passwords for complexity and this can cause deploys set off into the world with weak passwords to fail at the very end in a way that is a bit of a bummer to recover from. If you need to set a custom password at deploy-time, you still can, but please be sure to use a strong one.
- Prevent a communication breakdown between `chef-automate` client and server that we observed in some cases due to a disagreement about certificates. We now reset properly when retrying a failed connection and expect this to improve the reliability of deploy.


## Bug Fixes
- We fixed a bug that surfaced when spaces made their way into your `no_proxy` environment variable.
- When proxy config was present for the notifications service, but no_proxy unset, we used strJoin on a nil value. This caused the templating engine to break and stop rendering the rest of the files. We fixed that.
- Instead of creating a segmentation violation, we now deploy Chef Automate respecting your proxy settings when invoking deploy as `http_proxy=$PROXY chef-automate deploy ...`.
- Fixed a templating error in automate-elasticsearch's `health_check`
- You can now request a trial license even if you do not check the 'allow chef to send me information` box.
- Fixed a bunch of issues with the Node Detail Page. Icons on the resources list on the match the color of their corresponding rollup tab above, the Action type shows up in the column now, and everything is aligned correctly