[In Progress] Workflow's Environment Variables
Definition
By default, every Task that runs generates a series of environment variables. These variables are invisible in the sense that you'll never see them in the platform but they can always be accessed by your scripts.
These environment variables can help your scripts be context-aware as they run, giving knowledge into the structure and placement of the Task in relation to other Tasks
original marketplace Variables = Marketplace Variables
Environment Variable Type | Variable Name | Example (these are not real) | Definition |
|---|---|---|---|
Alli Client Cred S3 information: |
| something-123ab321-ct94-09p3-c74d-520e7e2c7py3 | Used to read and write files to a client’s s3 bucket: how to |
| source=app/app=something/- | ||
| source=app/app=something/temp=true/exec=913c104v-a385-30ge-9fa7-3p12owg2ef3a/ | ||
| PASHQT8HPAUNWW3LRPRA | ||
| AxUAQhO9Kj0/SNE7YNUnpElbvv0EP3U8N6N1eP817 |
[YES] Alli Client Cred Redshift information . How To
ALLI_DATA_REDSHIFT_URLALLI_DATA_REDSHIFT_HOSTALLI_DATA_REDSHIFT_PORTALLI_DATA_REDSHIFT_DATABASEALLI_DATA_REDSHIFT_USERALLI_DATA_REDSHIFT_PASSWORDALLI_DATA_REDSHIFT_IAM_ROLEALLI_DATA_REDSHIFT_KMS_KEY_ID
Alli Client Information.
ALLI_CLIENT_IDALLI_CLIENT_SLUGALLI_CLIENT_TIMEZONE
Dividing Logs. How To
LOG_BREAK
Alli OAUTH variables. How To
ALLI_OAUTH_TOKENALLI_OAUTH_TOKEN_TYPE
Google Cloud information. How To. For Google Sheets
ALLI_GOOGLE_CLOUD_CREDENTIALSALLI_GOOGLE_CLOUD_PROJECT
Workflow / Task / Execution Variables
[old] Shipyard Variables (needs update)
Name | Example | Definition |
|---|---|---|
|
| Set to the UUIDv4 of the Organization that the Vessel belongs to. |
|
| Set to the name of the Organization that the Vessel belongs to. |
|
| Set to the UUIDv4 of the Project that the Vessel belongs to. |
|
| Set to the name of the Project that the Vessel belongs to. |
|
| Set to the UUIDv4 of the Blueprint that the Vessel is built from. In the case of a Code Vessel, the ID will not be UUIDv4. |
|
| Set to the name of the Blueprint that the Vessel is built from. |
|
| Set to the UUIDv4 of the Vessel that the Log belongs to. |
|
| Set to the name of the Vessel that the Log belongs to. |
|
| Set to the UUIDv4 of the current Log that is running. |
|
| Set to the working directory that your Vessel is set to do its work in. |
|
| Set to the name of the Git repository selected for Code. Only set when the Vessel is connected to Git. |
|
| Set to the directory where the Git repository root was cloned. Only set when the Vessel is connected to Git. |
|
| The time at which the Vessel started running. Formatted using the RFC3339 standard. |
|
| The time at which the Vessel started running. Formatted using the RFC3339 standard. |
|
| The year of the Vessel start time. |
|
| The month of the Vessel start time in format 01-12. |
|
| The day of the Vessel start time in format 01-31. |
|
| The hour of the Vessel start time in format 0-23. |
|
| The minute of the Vessel start time in format 0-59. |
|
| The second of the Vessel start time in format 0-59. |
|
| The millisecond of the Vessel start time in format 0-999. |
|
| The number of seconds since the Unix epoch. |
Fleet Environment Variables
When a Vessel is run as part of a Fleet, the following Environment Variables will be available. For an overview of Upstream, Currentstream, and Downstream read our Glossary of Terms.
Name | Example | Definition |
|---|---|---|
|
| Set to the UUIDv4 of the Fleet that the Vessel belongs to. |
|
| Set to the name of the Fleet that the Vessel belongs to. |
|
| Set to the UUIDv4 of the current Fleet Log that is running. This ID will be constant for all Vessels in the current run. |
|
| The position of the current Vessel in the currentstream. This value is 0 based. Useful for splitting tasks into chunks dynamically and consistently. |
|
| The number of Vessels that ran upstream. |
|
| The number of Vessels running in the currentstream. |
|
| The number of Vessels that will run downstream. |
|
| A comma-separated list of Log IDs from Vessels that ran upstream. The order of the IDs will match the corresponding upstream environment variables, but may change with every run. |
|
| A comma-separated list of Log IDs from Vessels that are running in the currentstream. The order of the IDs will match the corresponding currentstream environment variables, but may change with every run. |
|
| A comma-separated list of Log IDs from Vessels that will run downstream. The order of the IDs will match the corresponding downstream environment variables, but may change with every run. |
|
| A comma-separated list of Vessel IDs from Vessels that ran upstream. The order of the IDs will match the corresponding upstream environment variables, but may change with every run. |
|
| A comma-separated list of Vessel IDs from Vessels that are running in the currentstream. The order of the IDs will match the corresponding currentstream environment variables, but may change with every run. |
|
| A comma-separated list of Vessel IDs from Vessels that will run downstream. The order of the IDs will match the corresponding downstream environment variables, but may change with every run. |
|
| The time at which the Vessel started running. Formatted using the RFC3339 standard. |
|
| The time at which the Vessel started running. Formatted using the RFC3339 standard. |
|
| The year of the Fleet start time. |
|
| The month of the Fleet start time in format 01-12. |
|
| The day of the Fleet start time in format 01-31. |
|
| The hour of the Fleet start time in format 0-23. |
|
| The minute of the Fleet start time in format 0-59. |
|
| The second of the Fleet start time in format 0-59. |
|
| The millisecond of the Fleet start time in format 0-999. |
|
| The number of seconds since the Unix epoch. |
|
| The path to the file that will be optionally created if headers are provided in the webhook invocation. |
|
| The path to the file that will be optionally created if a body is provided in the webhook invocation. |