Project Variables
Project variables are tied to a project and can be given a name, value, and a toggle between public/protected. They can also have an optional description to help identify what the variable is to be used for. The variable name must adhere to the following rules and must:
- not begin with
PROJECT_ - not begin with
CONSTELLATION_ - be at least 1 character long
- not be longer than 255 characters
- match the regex
^[a-zA-Z][a-zA-Z0-9_]{0,254}$
The value must adhere to the following rules:
- be at least 1 character long
- not be longer than 8192 characters long
Variable values can be updated at any time, regardless if they’re public or protected.
Variables can be used in context-aware places, such as in project action jobs. They can be used in either open ($MY_VARIABLE) or closed (${MY_VARIABLE}) format. The $ can be escaped with a backslash \, such as \$NO_LONGER_A_VARIABLE which will be rendered as normal text. Variables that could not be found during parsing will remain and not be replaced.
Public variables
Section titled “Public variables”Public variables can be read by project members at any point. These variables must not contain any secrets. If you accidentally save a secret to a public variable it should be considered compromised and should be rotated.
Protected variables
Section titled “Protected variables”Protected variables can’t be read by anyone, however, they will be seen if included in Email and API actions jobs when they run.