With vRealize Orchestrator 8.1 or higher it is possible to use PowerShell, NodeJS, and Python for tasks in vRealize Orchestrator workflows in addition to the traditional Javascript. As PowerShell support was added, it wasn’t necessary to add a PowerShell host to run PowerShell scripts anymore.
We can now use the following runtimes in our action and workflow scripts:
- Python 3.7
- Node.js 14
- PowerCLI 11/Powershell 6.2
- PowerCLI 12.3.0/Powershell 7.1
OOTB, the PowerCLI runtime includes PowerShell and the following modules:
- VMware.PowerCLI
- PowerNSX
- PowervRA
But to use additional modules in these polyglot scripts, we had to include dependencies by adding them as a ZIP package, which was a quite tedious work.
With vRealize Orchestrator 8.8 or higher, we can now add modules and libraries for use in our vRealize Orchestrator scripts as dependencies directly from the vRealize Orchestrator Client.
In this example, we’ll investigate how to create a script environment with an additional module for PowerShell.
