Removal of Chef Automate Workflow services and upgrade Journey from 4.13.0

The Automate Workflow product has been EOL since 2020, and maintaining the code in the repository requires CVE fixes and updating the dependencies with the latest packages. The Automate Workflow services use Habitat's core/curl package as a dependency. Since we are upgrading the core/curl package, we must follow the same standards we do for other components in terms of building and testing the Automate Workflow components. Since Workflow is an EOL component and leads to CVEs related to various packages, we want to remove the Automate Workflow related components from the Automate code. The customers upgrade journey to Automate 4.13.x may be affected if they have the Workflow services active in their Automate configuration. This article covers the related scenarios and the resolution steps the customer must follow to fix the issue and upgrade to the latest Automate version.

Was this article helpful?

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.