Hello all I am new to Pulumi and we are planning to migrate

Question

Hello all I am new to Pulumi and we are planning to migrate our application from a private cloud to Microsoft Azure So far we have always worked with Azure CLI or directly in Azure Portal for the purpose of validation and proof of concept We would like to deploy the resources using Pulumi and therefore I have started installing Pulumi and going through the Getting Started section of the doc Azure TypeScript The problem I am having occurs in the context of `pulumi up` When I run the command more or less nothing is done That means the processing time is about 10secs and the only thing I get is a headline `Previewing update appservice test ` without any content and afterwards a further headline `Resources ` also without any content A screenshot of the terminal window in VSCode is attached The behavior accours which each pulumi example code which I tested A call to `pulumi up logtostderr v=9 debug 2 gt out txt` shows the following error text in out txt I0801 10 36 55 680367 14836 host go 486 Error closing nodejs language plugin during shutdown ignoring 1 error occurred TerminateProcess Access is denied see attachment for full ou txt file A colleague of mine who works at another site has the identical error behavior I hope someone of aou can help use thanks in advance for your support

limited-rainbow-51650 · Answer

Hello < few lizard 48557> could you run `pulumi about` for me and paste the results

few-lizard-48557 · Answer

```PS C workspace azure ts appservice gt pulumi about CLI Version 3 37 2 Go Version go1 17 12 Go Compiler gc Plugins NAME VERSION azure native 1 67 0 nodejs unknown Host OS Microsoft Windows 10 Enterprise Version 10 0 19044 Build 19044 Arch x86 64 This project is written in nodejs executable= C Program Files nodejs node exe version= v14 16 0 Backend Name LO6 C 000CU URL file ~ User DE wolfsch6 Organizations Pulumi locates its logs in C Users wolfsch6 AppData Local Temp by default warning Failed to get information about the Pulumi program s plugins Found C workspace azure ts appservice package lock json but not npm unable to find program npm exe warning Failed to get information about the current stack No current snapshot PS C workspace azure ts appservice gt ```

limited-rainbow-51650 · Answer

This looks similar to this issue <https github com pulumi pulumi issues 3590> Your `pulumi about` output mentions that it can t find `npm` Does NodeJS start correctly when you run `node v` separately

few-lizard-48557 · Answer

Hi Ringo and thank you for your feedback Nodejs runs at this machine proper with several Repos `node v` shows V14 16 0

limited-rainbow-51650 · Answer

< few lizard 48557> for `pulumi about` any reason it can t find `npm` on your system

limited-rainbow-51650 · Answer

and referring back to the linked ticket do you have a proxy configured which might not correctly discard `localhost` or `127 0 0 1`

few-lizard-48557 · Answer

Hi Ringo I just checked the link you forwarded but I m not sure whether I do fully understand the information which is posted I have an authentification proxy px exe installed The configuration of this proxy px ini is the following

few-lizard-48557 · Answer

Concerning `npm` I can call it in the VSCode terminal where I also run `pulumi up` and there it works

limited-rainbow-51650 · Answer

The `noproxy` line is what I was after Pulumi uses a network GRPC protocol to communicate between the language host the engine and the provider binaries all locally on your machine If these network connections albeit locally are obstructed then Pulumi doesn t work correctly In your case the proxy is correctly configured as far as I can see not to proxy for connections on your own machine `127 0 0 ` and internal private networks `10 ` `192 68 `

few-lizard-48557 · Answer

I have now added 127 0 0 1 and localhost to the `noproxy`configuration restarted the console and tried `pulumi up` again = gt unfortunately without success That was just a helpless attempt from my side

few-lizard-48557 · Answer

Do you have any other idea how we can force the system to tell us what exactly is going wrong behind the scenes

limited-rainbow-51650 · Answer

Unfortunately not at the moment This week Pulumi is having a company wide refresh week I can t consult any of the core engineers this week unfortunately

few-lizard-48557 · Answer

Hello Ringo your tip with the proxy configuration was a hot tip for me and I would like to thank you expressly for it and I have also been able to find out in the meantime where exactly the dog is buried in the proxy configuration So here is the resolution to the proxy configuration for my computer in the hope that it may still be useful for others So the whole proxy configuration is apparently a 2 stage thing i e on the one hand there are entries in the environment variables which are `HTTP PROXY ` and `HTTPS PROXY `which on my computer forward to the authentication proxy Px exe which listens on port 3128 In addition there is an further proxy entry `NO PROXY localhost ` in the environment variables In NO PROXY the entry 127 0 0 1 is missing on my system which probably means that the requests for this ip are forwarded to the PX proxy This is the case for the GRPC communication between the language host and the engine but the PX proxy has configured an exclusion for 127 0 0 1 and somehow the instances involved cannot handle this in a proper way I have now added the exclusion 127 0 0 1 to the environment variable `NO PROXY 127 0 0 1 localhost ` which probably means that a request to this address will not be forwarded to the PX exe proxy and everything now works as expected i e by calling the command `Pulumi up` I get a preview of all Azure resources that are created during the call Many thanks again for the fast and good support

limited-rainbow-51650 · Answer

Glad I could help you out Have fun with Pulumi

few-lizard-48557 · Answer

thumbsup

limited-rainbow-51650 · Answer

This one was worth mentioning on our Troubleshooting page <https github com pulumi pulumi hugo pull 1797>