Overview #
The order of inheritance matters if a variable contains the same name at different levels (Environment, Project, or Workflow). For instance, if you created an Environment variable called “Variable 1”, and a Project variable of the same name, the Project variable would be used by any workflows within that Project. The order of inheritance is as follows:
- Environment Variables are inherited by any workflow running in that environment.
- Project Variables with the same name as an Env Var will be used instead of the Environment Variable for any workflows within that Project.
- Workflow Variables with the same name as a Project Variable or Environment Variable will be used instead, for that specific workflow.
- Task Variables with the same name as a Workflow Variable, Project Variable or Environment Variable will be used instead, for that specific task.
Information #
Standard Environment Variable rules apply across environments. For example:
- An Environment variable called “Variable 1” in the Dev environment will only apply to workflows running in Dev.
- An Environment variable called “Variable 1” in the Prod environment will only apply to workflows running in Prod.
Inheritance Priority #
When the same Variable name exists at multiple levels, the highest priority level is used. This will always be the lowest level of configuration e.g a task.
English