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 is happening because I'm waiting on slow-to-create resources, btw :wink: thanks!

My first thought would be to see if I could do anything about that timeout time limit, but I haven’t used Circle CI

That said I think short of increasing verbosity I’m not sure there is a way to get circumvent that timeout without automation api

You could write an app with automation API that gives you regular log message if the update is still running to get around that, but you would lose some of the pretty well formatted logs of using the CLI, though that may not matter inside a pipeline

what I'd love is a configurable interval to display a "waiting" message a la `pulumi up --yes --wait-message-interval=300`

that would be nice and I suspect you wouldn't be the only one to find it useful in pipelines that will timeout like that. Maybe open an issue?

slow deploying resources can be a bit of a pain for sure

Issue created - please upvote if you find this useful
<https://github.com/pulumi/pulumi/issues/6574>