This message was deleted.

subprocess.Popen

essentially runs your shell script in its own shell process. I don’t know much about `gcloud auth`If

gcloud auth

is simply setting env vars, that won’t work with triggering Pulumi commands via automation SDK in Python since Pulumi won’t “see” those environment vars. You will have to find a way to set authentication context that persists beyond just the shell script’s environment and is available/accessible in the Python

venv

when Pulumi runs as well.

Hi @clever-sunset-76585 thanks for the reply. What I am unable to find anywhere in the documents is what should be the value of the PULUMI_ACCESS_TOKEN if I use my own managed backend. I am not sure what values I should even set for this, and if I set the BACKEND_URL env var alone its throwing an error wrt to authentication

What I am unable to find anywhere in the documents is what should be the value of the

PULUMI_ACCESS_TOKEN

if I use my own managed backend. I am not sure what values I should even set for this

That should be your Pulumi account’s access token. Is your

BACKEND_URL

self-managed, or are you using our service (

<https://api.pulumi.com>

)? You can access the Access Tokens page for your Pulumi account by going to https://app.pulumi.com/account/tokens

my backend url is self managed, its a gcp bucket

my backend url is self managed, its a gcp bucket

what would be the access token for self managed backend ?

Ah yes I see that you mentioned that in your original message. There is no need for a Pulumi access token for self-managed backends. The issue here is that your Pulumi does not “see” the Google credentials you are setting via

subprocess.Popen

as I mentioned here https://pulumi-community.slack.com/archives/C01PF3E1B8V/p1621988033086700?thread_ts=1621983858.086600&cid=C01PF3E1B8V

Thanks, I will try that Praneet