No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This verbose logging should only be needed for somewhat advanced diagnostics. What logging was it you were looking for that you didn’t get automatically?

If this verbose logging is indeed what you were looking for - curious what you think would be the best place to add documentation on this (the raw flags are listed there - and we have docs on this at <https://www.pulumi.com/docs/troubleshooting/#verbose-logging> - where else could we add this to be more discoverable?)

I went to the logging because I was trying to understand an odd issue with the `azure-cs-functions-raw` sample, where a change to the app in the `functions` directory (which had been built and published via `dotnet publish`) which was then deployed via `pulumi up` exhibited some odd behaviour - sometimes I see the new code running, sometimes I don’t, sometimes I briefly do… it seems a reload of the app in Azure portal is needed to properly get things running (which the sample doesn’t do).

So wanted the logging to see a bit more about the order of Pulumi’s interaction with the Azure resources, management API calls, etc.