Kyle Dixler

@Zaid-Ajaj could templates be kept in mind when drafting the design doc for #1052 When going through the `pulumi new` flow, it prompts for config values, but after running `pulumi...

sure. wow the repro hangs my version of pulumi with no feedback. notes for later ``` I0729 08:39:00.855261 2918318 api.go:239] Making Pulumi API call: https://api.pulumi.com/api/cli/version I0729 08:39:14.863516 2918318 pulumi.go:259] error...

Not that it adds much, but I checked that v3.24.1 before #8710 also has this issue.

@cnunciato I see that changing ```typescript this.bucket.onObjectCreated("handler", () => this.handler()); ``` throws this error ``` Diagnostics: pulumi:pulumi:Stack (9168.pulumi-dev): error: Error serializing function '' function '': which could not be serialized...

To be more clear, standard out and the log messages are concatenated and the boundary isn't clear which makes debugging confusing.

Given how we do logging, stdout, logs, stderr are separate because logs are categorized by resource with the stack being the default resource. This is by design.

I'm looking at the events now and this does seem like a bug [](https://asciinema.org/a/PzuiTXp5RatOmOAbzIoFCjoxl)

one of the concerns with this is when a directory is not readable as we are outputting a new file. if a company has a policy for securing docker images...

> > if a company has a policy for securing docker images by disabling write permissions to directories, they may be unable to upgrade pulumi-language-go without it breaking. > >...

> The advantage of ~/.pulumi is then we can do `pulumi prune` command to get rid of that. I don't know when we'd know automatically that it is a good...