Ability to set gRPC ports for debugging

[solomonshorser]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The problem: I'm debugging a plugin which I think is sending the wrong data to a cloud service. I've tried debugging with a proxy application to intercept and inspect the messages being sent to the cloud service, but I am running into problems since it looks like pulumi's components communicate with each other using gRPC with random port numbers, and this proxy breaks pulumi.

The requested feature: The ability to specify fixed port numbers for gRPC so that I can monitor and inspect messages with applications such as Charles Proxy. Maybe a flag like this: --grpc_port 5544

I'm open to other ideas, if they will let me use a proxy to inspect the messages that pulumi is sending and receiving.

Affected area/feature

CLI

[Frassle]

There's an envvar you can set to tell pulumi to attach to a specific port for a specific provider (#8979) if you set PULUMI_DEBUG_PROVIDERS=provideName:portNumber the engine will attach to that provider rather than starting a new instance of the provider on a random port.

[solomonshorser]

@Frassle Cool! I'll give that a try. Is there a list of other useful pulumi environment variables?

[Frassle]

pulumi env will print a list with descriptions.

[solomonshorser]

pulumi env will print a list with descriptions.

Cool feature, though it seems to be missing PULUMI_CONFIG_PASSPHRASE and PULUMI_DEBUG_PROVIDERS - or does it only print env vars that are not set?