VMware Aria Automation 8.16

8.18 8.17 8.16 8.14 8.13 all
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands Русский 繁體中文 English

Automation Orchestrator
 script environments

You can now add modules and libraries for use in your
Automation Orchestrator
 scripts as dependencies directly from the
Automation Orchestrator Client
.
In previous releases of
Automation 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
Automation 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
Automation Orchestrator
.
Similarly to other
Automation Orchestrator
 objects such as workflows and actions, environments can be exported to other
Automation Orchestrator
 deployments as part of a package.
  1. Log in to the
    Automation Orchestrator
     Client.
  2. Navigate to
    Assets
    Environments
    , and click
    New Environment
    .
  3. Under the
    General
     tab, enter a name for your environment.
  4. Enter a description, version number, tags, and group permissions for the action.
    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. Edit the memory limit and timeout properties.
    4. Under
      Dependencies
      , click
      Add
      , and enter the following values:
      Name
      lodash
      Version
      4.17.21
  6. Click
    Add
    .
  7. 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.
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
Automation Orchestrator
 action.

Content feedback and comments