pulumi runs started by this tool seem to ignore some envs

[smktpd]

What happened?

Running pulumi preview via this extension with envs PULUMI_SKIP_UPDATE_CHECK=true and PULUMI_DISABLE_AUTOMATIC_PLUGIN_ACQUISITION=true results into Pulumi still making request to CloudFront/GitHub hosts, while a similar manual invocation of that command with these 2 envs in a terminal results into Pulumi not making requests to CloudFront/Github hosts.

Example

The bug basically boils down to launch.json having

{
    "version": "0.2.0",
    "configurations": [
        {
            ...,
            "env": {
                "PULUMI_SKIP_UPDATE_CHECK": "true",
                "PULUMI_DISABLE_AUTOMATIC_PLUGIN_ACQUISITION": "true"
            }
        }
    ]
}

vs running export PULUMI_SKIP_UPDATE_CHECK=true && export PULUMI_DISABLE_AUTOMATIC_PLUGIN_ACQUISITION=true && pulumi preview.

Only the latter example doesn't lead to pulumi sending requests to CloudFront/GitHub.

Output of pulumi about

CLI
Version 3.147.0
Go Version go1.23.5
Go Compiler gc

Plugins
KIND NAME VERSION
resource gitlab 8.1.0
resource pulumi_gitlab_helpers 1.1.0
resource pulumi_gitlab_rbac 1.1.2
resource pulumi_gitlab_structure 1.0.5
resource pulumi_ldap_group_provider 1.0.5
language python 3.147.0

Host
OS darwin
Version 14.6
Arch arm64

This project is written in python: executable='{redacted}/pulumi-projects/gitlab-rbac/venv/bin/python' version='3.9.6'

Current Stack: organization/gitlab-rbac/{redacted}

TYPE URN
pulumi:pulumi:Stack urn:pulumi:{redacted}::gitlab-rbac::pulumi:pulumi:Stack::{redacted}
pulumi:providers:gitlab urn:pulumi:{redacted}::gitlab-rbac::pulumi:providers:gitlab::default_8_1_0
gitlab:index/groupMembership:GroupMembership urn:pulumi:{redacted}::gitlab-rbac::gitlab:index/groupMembership:GroupMembership::{redacted}

Found no pending operations associated with {redacted}

Backend
Name {redacted}
URL {redacted}
User {redacted}
Organizations
Token type personal

Dependencies:
NAME VERSION
boto3 1.35.14
debugpy 1.8.12
pip 25.0
pulumi_gitlab_helpers 1.1.0
pulumi_gitlab_rbac 1.1.2
pulumi_gitlab_structure 1.0.5
pulumi_ldap_group_provider 1.0.5
setuptools 58.0.4

Pulumi locates its logs in /var/folders/{redacted} by default

Additional context

It seems to apply other envs (like AWS_DEFAULT_REGION, AWS_SECRET_ACCESS_KEY, AWS_ACCESS_KEY_ID, AWS_S3_ENDPOINT and PULUMI_CONFIG_PASSPHRASE) juuust fine.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[EronWright]

This issue might be resolved by a recent PR, which fixes an issue that the environment variables weren't passed to the initial 'stack selection' call to the automation API.
#27

Let's re-test with v0.3.0 of the extension, which will have the above fix, and go from there. Thanks!

[smktpd]

Unfortunately, the behavior didn't change.

[smktpd]

I've just noticed that the extension has settings:

This button opens my *.code-workspace file and adds

	"settings": {
		"pulumi.env": {
			
		}
	}

there. Moving the value of .configurations[0].env key from my launch.json to the value of "pulumi.env" in my *.code-workspace seems to have led to the very same result: the AWS-related variables got loaded fine, but the PULUMI_SKIP_UPDATE_CHECK and PULUMI_DISABLE_AUTOMATIC_PLUGIN_ACQUISITION seem to be ignored again (pulumi attempts to send requests to CloudFlare/GitHub hosts again).