Environment Variables¶
There are per-plan differences on what can be specified which you can see below.
Community (Free) users' environment variables¶
Community (Free) users can control anything that is repository config, via environment variables.
This, for instance, allows a more straightforward way to default minimumReleaseAge
Community (OSS) users' environment variables¶
Community (OSS) projects have the same access as Community (Free) users.
Enterprise and Mend AppSec users' environment variables¶
If you are a paying Mend customer, in addition to being able to control repository config, you also have access to control the following environment variables:
| Variable | Config option |
|---|---|
RENOVATE_ALLOWED_COMMANDS |
allowedCommands |
RENOVATE_ALLOWED_ENV |
allowedEnv |
RENOVATE_ALLOWED_HEADERS |
allowedHeaders |
RENOVATE_ALLOWED_UNSAFE_EXECUTIONS |
allowedUnsafeExecutions |
RENOVATE_ALLOW_PLUGINS |
allowPlugins |
RENOVATE_ALLOW_SCRIPTS |
allowScripts |
RENOVATE_ALLOW_SHELL_EXECUTOR_FOR_POST_UPGRADE_COMMANDS |
allowShellExecutorForPostUpgradeCommands |
RENOVATE_CUSTOM_ENV_VARIABLES |
customEnvVariables |
RENOVATE_INHERIT_CONFIG |
inheritConfig |
RENOVATE_INHERIT_CONFIG_FILE_NAME |
inheritConfigFileName |
RENOVATE_INHERIT_CONFIG_REPO_NAME |
inheritConfigRepoName |
RENOVATE_INHERIT_CONFIG_STRICT |
inheritConfigStrict |