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

I don't know what your setup it but we use Tailscale too. We run Pulumi on Gitlab runners which have access to our Tailscale network to make calling private resources easier

The issue is that without any error output it's impossible to guess which provider and at which point it gets stuck. Is there an easy way to enable debugging output for our deployment?

<@U09QQ01M7MY> I'm finding better success in the GHA environment as well. Unfortunately that means we must do the orchestration in github actions

I haven’t tested to be sure, but I think with <https://www.pulumi.com/blog/controlling-the-cli-through-environment-variables/> you can enable verbose logging <https://www.pulumi.com/docs/support/debugging/logging/> by setting `PULUMI_OPTION_VERBOSE=11`

It’s probably easier to narrow this down locally by running pulumi in a container manually.