Manage task environment variables

Task environment variables are used to manage tenant-level predefined environment variables. Once enabled, these environment variables can be injected into training task containers to standardize runtime parameters, access URLs, feature flags, and other non-sensitive configuration.

​

Variable scope boundaries

Task environment variables are a tenant-level configuration. Whether they are injected into task containers and how naming conflicts with task-level variables are handled are governed by the training task creation and execution rules. Environment variables should not store highly sensitive secrets. When secrets or access credentials must be used, follow the platform security requirements and avoid exposing actual values in documentation, logs, commands, or public channels.

​

Create environment variables

1. Go to Config Management > TaskEnv Management.
2. Click Create.
3. Configure the environment variables.

   Parameter	Description
   EnvKey	The environment variable name can contain only English letters, digits, and underscores and cannot start with a digit. It must be unique and cannot contain =, spaces, line breaks, Chinese characters, full-width symbols, zero-width characters, or similar characters.
   EnvValue	The value injected into the task container must be a string. It can be 0, but cannot be empty or contain a NUL character.
   Hide this environment variable	When enabled, the variable value is hidden in the console.
   Enable Or Not	Enabled by default. When enabled, this environment variable is injected into training tasks by default.

4. Click Create.

After creation, ensure that the environment variable is enabled. When you create subsequent training tasks, the platform injects variables according to the rules for task environment variables.

​

Manage environment variables

After locating the target environment variable in Config Management > TaskEnv Management, you can update, disable, enable, or delete it in the Actions column.

• Update: Modify the variable value, visibility setting, or enabled status. Changes to environment variables may affect training tasks created or resubmitted later. Whether the changes affect running tasks depends on the training task runtime behavior.
• Disable / Enable: Control whether an environment variable continues to be injected into subsequent training tasks. If you no longer want tasks to use a variable, disable it first and check whether this affects task submission or execution.
• Delete: Delete environment variables that are no longer in use. Before deletion, ensure that no future training tasks depend on the variable; otherwise, scripts that require it may fail to start because of missing runtime configuration.

​

Next steps

• Create training tasks