Environment variables reference#
Variables used by dev simulation, pipeline drivers, or job sandboxes (map/vanilla/TypedJob workers). Secrets such as YT_TOKEN and S3_* are documented in Secrets.
Public environment vs secure_vault (production cluster)#
In prod mode, YTProdClient splits the merged operation env:
Plain
environment(visible in the YT UI for operations you can read): a small built-in set (YT_STAGE_NAME,YT_ALLOW_HTTP_REQUESTS_TO_YT_FROM_JOB, tokenizer artifact keys) plus any names listed underenvironment_public_keysfor that operation.secure_vault: everything else from the merged env, plusdocker_authwhendocker_imageis set, merged with anysecure_vaultyou pass through operation kwargs.
Jobs still receive vaulted keys under their normal names in the process environment when you use string mapper/vanilla/reducer commands (the client adds a stdlib promotion step). TypedJob code should call promote_secure_vault_environment() from yt_framework.yt.support.operation_secure_env early, or rely on YT_SECURE_VAULT_* names.
Dev mode does not split: the subprocess gets the full dict, since there is no YT spec UI.
Dev mode (YTDevClient)#
Variable |
When set |
Purpose |
|---|---|---|
|
Optional |
If |
Job sandbox (workers)#
Set by wrappers or TypedJob bootstrap (StageBootstrapTypedJob, command-mode scripts), not by you in typical pipeline configs.
Variable |
Set by |
Purpose |
|---|---|---|
|
Wrapper / |
Absolute path to |
|
Production job wiring |
Stage name; used by |
|
Dependency packaging |
Basename or relative path to the tokenizer tarball inside the sandbox (e.g. under archive root). |
|
Bootstrap (optional) |
Directory (relative to sandbox root) where the tarball is extracted; derived from |
|
Bootstrap |
Logical name for default extract dir |
See Tokenizer artifacts for how tarball paths and config relate.
Checkpoint / model files in jobs#
Variable |
Typical source |
Purpose |
|---|---|---|
|
Framework checkpoint mounting |
Path to mounted model checkpoint in the operation sandbox (see Checkpoint management). |