You can now add modules and libraries for use in your vRealize Orchestrator scripts as dependencies directly from thevRealize Orchestrator Client.

In previous releases of vRealize Orchestrator you could only add dependencies to your scripts by adding them to a ZIP package. You can now add modules and libraries you want to use as dependencies in your scripts by creating an environment directly from the vRealize Orchestrator Client. Your environment can include multiple modules and libraries for use in your scripts.

In this use case, you are creating an lodash environment that you can use for your Node.js scripts in vRealize Orchestrator.

Note: Similarly to other vRealize Orchestrator objects such as workflows and actions, environments can be exported to other vRealize Orchestrator deployments as part of a package.

Procedure

  1. Log in to the vRealize Orchestrator Client.
  2. Navigate to Assets > Environments, and click New Environment.
  3. Under the General tab, enter a name for your environment.
  4. (Optional) Enter a description, version number, tags, and group permissions for the action.
    Note: The ID is generated automatically after the environment is created.
  5. Set the runtime environment and add dependencies and dependency variables.
    1. Select the Definitions tab.
    2. Under Runtime Environment, verify that Node.js is selected.
    3. (Optional) Edit the memory limit and timeout properties.
    4. Under Dependencies, click Add, and enter the following values:
      Option Description
      Name lodash
      Version 4.17.21
  6. Click Add.
  7. (Optional) Add environment variables.
  8. To finish creating your new script environment, click Create.
  9. After the environment is created, select the Download Logs tab on the environment editor page and validate that the lodash library is downloaded successfully.

Results

What to do next

You can now use lodash in workflow scripting tasks or actions by selecting the environment from the Runtime Environment drop-down menu of your workflow scripting schema element or vRealize Orchestrator action.