UPDATE: We’ve identified a bug that requires the users to login using the Full name previously provided during the `/#/setup` mode. We are going to release a new package to rectify this soon.
Chef Compliance 0.15.2 is now available from the Chef downloads site. This is a minor release update which is recommended for all users of Chef Compliance. Here are the enhancements and bug fixes included in this release:
- Add CIS profiles for Red Hat Enterprise Linux 7
- Turn off ssh compression by default for broader ssh support
- Packages scan output to be logged with debug verbosity
- Use InSpec 0.14.8
- Chef Compliance API and WebUI to use database enhancements, eg. UUID as object identifier
- API calls that create objects, return json with object id and name
- WebUI lists to use Name as the first column instead of ID
- API: Sort jobs and keys by name
- Scheduled jobs not running after Feb 29th
- Show correct package version in Chef Compliance UI
- Restrict length of node name for bar-chart
- Dashboard node view not loading fields for organizations
- Remove duplicate user logo from the interface
- New user password field should hide password
- Fix 404 error messages exposed when deleting teams
Upgrade instructions for Chef Compliance are found here.
This release makes a substantial number of database improvements, especially it uses UUIDs as unique identifier for all stored items now. It’s recommended to do a database backup before the upgrade. You can do this using these two bash commands:
export THEDATE=$(date '+%Y-%m-%d-%H-%M-%S') su - chef-pgsql -c "/opt/chef-compliance/embedded/bin/pg_dumpall -c | gzip --fast > /tmp/postgresql-dump-$THEDATE.gz"
In the event that a database restore is needed, it can be done with the following command:
gunzip -c /tmp/postgresql-dump-$THEDATE.gz | su - chef-pgsql -c "/opt/chef-compliance/embedded/bin/psql -d postgres"