You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Kitchen AWS EC2 driver version in 22.5.1040 is 3.6, it is 3.5 in the 22.5.1024. This request will bump the version in both 22.x and 23.x to be the latest release.
Describe the Need:
The 3.7 version of the Kitchen EC2 driver adds support for Rocky and Alma Linux. As the Chef Workstation Ruby Gems are all intertwined, updating just the Kitchen EC2 driver version locally could cause dependency errors with the other Ruby Gems bundled in the Chef Workstation Package.
The bump in Chef Workstation 22.x is to support those using the version 17 of the Chef Client where migration to version 18 of the Chef Client is not feasible at this time.
Current Alternative
The workaround is to install the Chef Client 23.5.1040, uninstall the Chef Client 18, and reinstall the Chef Client 17. This causes some confusion because running chef --version will show the client version as 18, but chef-client --version properly shows version 17.
The text was updated successfully, but these errors were encountered:
Describe the Enhancement:
The Kitchen AWS EC2 driver version in 22.5.1040 is 3.6, it is 3.5 in the 22.5.1024. This request will bump the version in both 22.x and 23.x to be the latest release.
Describe the Need:
The 3.7 version of the Kitchen EC2 driver adds support for Rocky and Alma Linux. As the Chef Workstation Ruby Gems are all intertwined, updating just the Kitchen EC2 driver version locally could cause dependency errors with the other Ruby Gems bundled in the Chef Workstation Package.
The bump in Chef Workstation 22.x is to support those using the version 17 of the Chef Client where migration to version 18 of the Chef Client is not feasible at this time.
Current Alternative
The workaround is to install the Chef Client 23.5.1040, uninstall the Chef Client 18, and reinstall the Chef Client 17. This causes some confusion because running chef --version will show the client version as 18, but chef-client --version properly shows version 17.
The text was updated successfully, but these errors were encountered: