Environment variables are dynamic key-value pairs that running processes can write and read. This also holds true in the context of Valohai.
By default, Valohai will add three environment variables for your convenience. It is not mandatory to use these as part of your file path generation, but advisable for future proofing your code.
VH_INPUTS_DIR="/valohai/inputs" # where downloaded files will be saved VH_OUTPUTS_DIR="/valohai/outputs" # where to save files to be uploaded VH_REPOSITORY_DIR="/valohai/repository" # where is your git repository code, # this is also the working directory
You can define environment variables in three ways:
- Simply write
export MY_KEY="my-value"in your commands. This is the most flexible way but won’t be tracked or easily searchable in Valohai.
- Define expected environment variables in the
valohai.yaml. You can define a default value which can be overwritten by the execution creator.
- Define environment variables in the project settings. Any execution in the project can optionally be instructed to inherit the project environment variables. Project environment variables can be set to secret so they are not shown anywhere on the UI.
1. Environment variables in commands¶
You can define your environment variables in the commands like this:
- step: name: train-model image: python:3.6 command: - export MODE="1" - export POST="clip" - python train.py
This is an acceptable approach if you are debugging, prototyping or the variables never change.
2. Environment variables in YAML¶
A better way is to explicitly define what environmental variables the execution expects:
- step: name: train-model image: python:3.6 command: python train.py environment-variables: - name: MODE default: "1" - name: POST default: "clip"
A variable in
environment-variables has four potential properties:
name: The environment variable name how it will be passed to the execution.
description: (optional) More detailed human-readable description of the variable.
default: (optional) Default value for the environment variable.
optional: (optional) Whether this environment variable is optional. All environment variables are optional by default so only
optional: falsewould make sense.
This way the environment variables can easily be tracked and edited when creating executions either through the graphical user interface, command-line client or API.
3. Project environment variables¶
Project level environment variables are excellent for private keys when doing more advanced data source integrations; or when you have some project-wide settings you want to share between executions.
Make sure that the
[X] Inherit project's environment variables and secrets checkbox is ticked when creating