External Package Dependencies
Definition
Every language that Alli Workflow supports has packages that can be installed to enhance the functionality and simplicity of your scripts. If your script uses an external package, you'll have to tell Alli Workflow what packages to install before the script can run successfully.
There are 2 options in the platform for installing packages. How you enter this information varies by language.
If you're uploading code directly to Alli Workflow, we recommend installing packages using the Packages Panel so that team members can quickly view and change the version.
If you're using a Git connection, we recommend including a packages file in the root directory of your repository. Alli Workflow will automatically find this file and install dependencies.
You must choose one option or the other. Using both simultaneously will result in packages not being installed properly.
Setup
Option 1 - Use the Packages Panel
Python
Bash
Node
Option 2 - Uploading a Packages File
Python
Bash
Node
Additional Notes
-
Because Tasks are containerized, the packages you install will only be available for that Task.
System Package Dependencies
Definition
For Python and Node Tasks, in addition to the language packages that are available in each, you may also install additional low level "system packages" for use by your code. With Alli Workflow’s current setup, these must be Debian Packages. These packages are installed using apt-get and get installed before language package. Typically, these only need to be included if they are a dependency for a language package you need to install.
Because Tasks are containerized, the System packages you install will only be available for that Vessel.
Screenshots