….plus on the Chocolatey site dependencies are listed for each application:Īdding the dependencies listed in step 1 and changing the application to install from vscode to vscode.install in step 2 resolved the issues. How did I know these were required to install first? Well, mostly because neither VS Code nor PowerShell Preview installed at first.Ī combination of looking through the logs of the playbook which complained about various things missing…… Note that the first step involves installing some supporting Chocolatey extensions, chocolatey-core.extension and chocolatey-windowsupdate.extension. The contents of _14_install_chocolatey_packages.yml are as follows: Chocolatey is a free software management automation tool for Windows, which can be used to install programs, and deploy runtime binaries or zipped files. Our job template in AWX is _14_install_chocolatey_packages: Our server currently has no applications installed: Of course you could instead include Chocolatey as part of your Windows base image. You’ll receive a warning during playbook execution if Chocolatey was installed. This module will first of all install chocolatey if it is not present on the system. In this example we’ll demonstrate how to install Visual Studio Code and PowerShell 7.0 Preview using the win_chocolatey Ansible module. 15 Scoop lets developers quickly set up a repeatable development environment. 14 13 Both have strong community support. Some bloggers recommend to install both Chocolatey and Scoop. In Part 15 of this series we’ll continue our journey with Ansible, Windows and PowerShell and look at how to install software packages via Chocolatey. Most other package managers (such as Chocolatey ) install applications in one central location, where they are usable by all the users on the system.
0 Comments
Leave a Reply. |