Open nweddle opened 5 years ago
Thanks for the reminder - we'll definitely look to add this in a future round of updates.
Just also to document this here, to be able to fully use the extension with Chef Workstation the current workaround is needed with Windows build agents. (Affects any tasks that use chef exec
e.g. Test Kitchen)
New-Item -ItemType SymbolicLink -Path "C:\opscode\chef-dk\" -Target "C:\opscode\chef-workstation\"
cp C:\opscode\chef-workstation\bin\chef C:\opscode\chef-workstation\bin\chef.bat
The copy is needed as the extension is looking for chef.bat, which is no longer present in Chef Workstation.
C:\opscode\chef-workstation\bin> ls chef*
Directory: C:\opscode\chef-workstation\bin
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 27/01/2020 11:11 26 chef
-a---- 27/01/2020 11:11 2940416 chef.exe
-a---- 27/01/2020 11:11 12674560 chef-analyze.exe
-a---- 27/01/2020 11:11 12135 chef-apply
-a---- 27/01/2020 11:11 56 chef-apply.bat
<snip>
Hi, any update on this? We would want to use chef workstation on Linux agents.
I would like the option to choose between installing Chef Workstation or ChefDK on my pipelines.
One benefit would be the ability to use
chef-run
on remote targets in some deployment scenarios.