--- title_tag: "Environment Variables | Pulumi CLI" meta_desc: A list of different environment variables the Pulumi CLI supports. title: Environment variables h1: Pulumi CLI environment variables meta_image: /images/docs/meta-images/docs-meta.png menu: cli: weight: 2 aliases: - /docs/reference/cli/environment-variables/ ---
Skips the minimum CLI version check used by Automation API to ensure compatibility. We do not recommend using this variable as it may result in unexpected behavior or confusing error messages from Automation API.
PULUMI_AUTOMATION_API_SKIP_VERSION_CHECK=true
Set this environment variable to authenticate into the Pulumi Cloud backend and bypass the access token prompt when running {{% md %}}`pulumi login`{{% /md %}}.
PULUMI_ACCESS_TOKEN="your-access-token"
Set this environment variable to use a specified backend instead of the default backend. See State and Backends for details on valid backend URLs.
PULUMI_BACKEND_URL="s3://your-pulumi-state-bucket"
Sets configuration for unit testing. Must be in JSON format.
This environment variable is ignored during normal Pulumi operations -- e.g., up
, preview
, etc.
PULUMI_CONFIG="{'project:myTag':'val1','project:mySecret':'val2'}"
Set this as an environment variable to protect and unlock your configuration values and secrets. Your passphrase
is used to generate a unique key for your stack, and configuration and encrypted state values are then encrypted
using AES-256-GCM
.
Read the change log
and Configuration and Secrets to learn more about Pulumi's configuration
and secrets management system.
PULUMI_CONFIG_PASSPHRASE="your-passphrase"
An alternative method to providing PULUMI_CONFIG_PASSPHRASE
. Set this to the path of a file that contains the passphrase value.
PULUMI_CONFIG_PASSPHRASE_FILE="/tmp/passphrase.txt"
Overrides the domain used when generating links to the Pulumi Cloud.
PULUMI_CONSOLE_DOMAIN="yourhost.domain.com"
As of v0.12.2
,
the promise leak experience has been improved and shows a simple error message. Set this environment variable to
get more verbose error messages when debugging promise leaks.
PULUMI_DEBUG_PROMISE_LEAKS=true
As of 1.0.0-beta1
,
input properties are no longer propagated to missing output properties during a pulumi preview
. If this causes issues
in your Pulumi program, set this to true
to enable the old behavior.
PULUMI_ENABLE_LEGACY_APPLY=true
As of v0.17.23
,
the detection of differences between the actual and desired state of a resource is left entirely up to that resource's
provider. This change can expose bugs in resource providers that lead to diffs being present even if the desired
configuration matches the actual state of the resource. Set this to 1
or true
to enable the old diff behavior.
PULUMI_ENABLE_LEGACY_DIFF=true
As of v0.16.18
,
a fix has been released to prevent the Pulumi CLI from loading the newest plugin for a resource provider instead of
the requested version. This has the potential to disrupt users that previously had working configurations. Set this
environment variable to opt into the legacy plugin load behavior.
PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=true
Overrides the folder where the Pulumi CLI stores its artifacts: plugins, workspaces, templates, and
credentials file. By default, artifacts are stored next to Pulumi binaries in ~/.pulumi
.
PULUMI_HOME="/path/to/artifacts"
Set this environment variable to opt-in to using yarn
instead of npm
for installing Node.js dependencies.
PULUMI_PREFER_YARN=true
As of v0.16.6
,
the Pulumi CLI uses python3
instead of python
when running a Python program. Set this environment variable to
run a different Python binary.
PULUMI_PYTHON_CMD="python-version-binary"
As of v2.0.0
,
an explicit confirmation was required when running in non-interactive mode. Set this environment variable to
make that explicit confirmation.
PULUMI_SKIP_CONFIRMATIONS=true
As of v0.17.9
,
you may skip the Pulumi version update check by setting this environment variable.
PULUMI_SKIP_UPDATE_CHECK=true
The presence of this environment variable (regardless of its value) strips color ANSI codes from text output to the terminal. See https://no-color.org/ for more details. When used with Automation API, this environment variable will strip color directives from the event logs.
NO_COLOR