Environment variables and secrets at the Group level
You can set both variables and secrets for a Group of checks.
For browser and multistep checks, you can set variables at the check level. See browser check variables and secrets for more details.
Secrets are available for Private Locations on agent version 3.3.4
and later. Secrets are available on CLI version 4.9.0
and later.
To ensure the integrity of Playwright artifacts (traces, videos and screenshots), the following are not scrubbed, even when saved as secrets: The characters /
and *
and the full or partial match of /artifact/
, https://
, http://
, *********
, and 123
.
Values of the keys sha1
, _sha1
, pageref
, downloadsPath
, tracesDir
, pageId
and any string that ends with sha1
will not be scrubbed from the Playwright trace, but will be scrubbed from the general check result.
Numbers are not scrubbed from the Playwright trace, but from the general check result.
Variable hierarchy
As checks are scheduled, Checkly merges the check, group and global environment variables into one data set and exposes them to the runtime environment. During merging, any check variable with the same name as a global or group variable overrides that variable.
Or, in other words: check variables trump group variables trump global variables.
You can make use of this by providing a default value for a specific variable at the global or group level, but allow that variable to be overridden at the group level or check level.
Last updated on January 29, 2025. You can contribute to this documentation by editing this page on Github