The Chef requirement for the deployment archive is now 14.x.x. With this update, some cookbooks had to be updated as well. The most relevant change was the update of the apache2 cookbook to 7.1.0 . With this update, the apache2::web_app definition is no longer available, which made the coremedia-proxy::webapp wrapper definition and the whole cookbook obsolete. Rendering a new virtual host configuration has now become less complex. Please visit the apache2 cookbooks documentation for more details.

The product specific cookbooks blueprint-lc3-sfcc , blueprint-cms9 , blueprint-lc3-ibm-wcs and blueprint-lc3-hybris have been merged into a single cookbook named blueprint-cmcc .

The blueprint-tomcat cookbook has been replaced with the blueprint-spring-boot cookbook.

The recipes blueprint-dev-tooling::rpm-build and blueprint-dev-tooling::rpm-install have been removed. If you still need to build rpms, please use one of the available maven plugins to wrap the spring-boot application jars. Spring-Boot jars are executable and easy to configure, removing all the complexity of a rpm build process.

The Chef attribute structure of the deployment archive has been changed slightly. For more details review the global/deployment/chef/MIGRATION.md in the workspace.

The example Chef roles have been reorganized. Similar to the removal of the product specific cookbooks, the product specific roles have been removed in favor of central roles for all products. The commerce system specific configurations can now be activated using the boolean Chef node attributes: