set the channel description: Troubleshoot problems installing Pulumi. Hopefully you never have to join this channel.

Hello, I'm trying to use pulumi for the first time but cannot get to login using cli, I have this

$ pulumi config
We need your Pulumi account to identify you.
Enter your access token from <https://app.pulumi.com/account>
    or hit <ENTER> to log in using your browser            : 
error: resource temporarily unavailable

Am I doing something wrong ? I already have an access token but cannot find out where to add it

Ok, solved, added the token as environment variable

@able-tomato-34262 Glad to hear you solved it! You should have been able to paste the token into that prompt, but I realize it may not have been obvious that's what the tool was asking you to do. Did you try that and it didn't work or was it just not obvious that what you were supposed to do?

Hello @bitter-oil-46081

Actually, when I got this error, I didn't have any chance to paste anything as it exited in error directly

But as a matter of facts, it's because I was executing pulumi inside a screen

When I got out of my screen, I had no problem

It's the same when I try

pulumi update

, I got this :

$ AWS_PROFILE=pulumi pulumi update
Previewing update of stack 'prod'
Previewing changes:

     Type                 Name               Plan          Info
 *   pulumi:pulumi:Stack  first-pulumi-prod  no change     
 +   ├─ aws:s3:Bucket     my-bucket2         create        
 -   └─ aws:s3:Bucket     my-bucket          delete        
 
info: 2 changes previewed:
    + 1 resource to create
    - 1 resource to delete
      1 resource unchanged

Do you want to perform this update?
  yes
> no
  details
error: confirmation cancelled, not proceeding with the update: read /dev/stdin: resource temporarily unavailable

As for the previous error, it exits directly with no possibility of choosing options

I tried to set my TERM for the same value as when I'm outside a screen but same error

Do you want me to create an issue ?

Yes. Please do, let me know what TERM ends up getting set in your screen by default.

You can pass

--yes

to pulumi update to prevent the prompt. In this case you may want to explicitly run a

pulumi preview

so you have a chance to see what is done. Really sorry you are having such problems. @able-tomato-34262.

Well, I'm confused @bitter-oil-46081, I rebooted my laptop, created a new screen and now it's working fine...

Even with the screen

TERM

So nothing to report here 😛

Hello there! First time installing Pulumi, trying to do it inside a container (mainly for CI / headless use cases), here's my experience so far: - the PATH env isn't correctly set by the script (tried both

alpine

and

ubuntu

as base images) - ANY command I try to run (

pulumi new

, for example) requires a login - not a fan of that at all - on top of that, the redirect URL is a localhost one with a random port, so there's no way I can interactively login from within a container. - edit for last two observations - found out about

pulumi login --local

, big fan of that 🙂

I would argue that the local login should be on by default

I don’t see local by default happening any time soon, pulumi is a product after all. But maybe in CI env something could be done.

@green-london-79864 Yep -

pulumi login --local

is the command to use to do local-only (which in particular means managing state file persistence and concurrency control yourself). We definitely want that option to be discoverable when needed - curious - where did you ultimately discover it? And where did you expect to see it? As @adventurous-jordan-10043 noted, we really want the default to be an experience that works great out of the box without need to worry about state file management - but we want the local option to be discoverable when needed.

the redirect URL is a localhost one with a random port, so there's no way I can interactively login from within a container.

Note that you can set

PULUMI_ACCESS_TOKEN

env var to provide the login information without need for interactive login. See https://pulumi.io/reference/cli/pulumi_login.html for details.

the PATH env isn't correctly set by the script (tried both

alpine

and

ubuntu

as base images)

We do attempt to write it to the

PATH

, so not sure why this is not working. We'll try to reproduce this and fix. FWIW - here's the implementation of the installer: https://github.com/pulumi/get.pulumi.com/blob/master/dist/install.sh#L116

Hey, @white-balloon-205! Thanks a lot for the response here: - regarding the login, I expected a reference in the installing / getting started doc - but that's fine, maybe I just wasn't paying enough attention there, and I understand trying to get people as familiar as possible with the cloud offering. - the token environment variable should do the trick for my use case, thanks for pointing that out! - the PATH observation was by no means a showstopper, just a heads up for it. All in all, I really enjoyed getting started with this and managed to create Kubernetes objects in no time and I expect to go ahead and also try provisioning cloud services next. Will surely document the process and let you know of any other small things I encounter. Thanks for the support!

hi, i did curl -fsSL https://get.pulumi.com | sh and got curl: (60)

looked around and found curl 'k' option to ignore TLS; now I am getting "could not determine latest version of pulumi..."

it looks like script isn't able to connect...which might have something to do with my corp proxy

I am behind NTLM auth

any suggestions on how to get past this?