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

Hello folks,
When using Pulumi Actions in Github (update or up commands), if for whatever reason a deployment doesn't work (ex: init container fails, imagepullBackOff, etc) Pulumi will wait until a timeout threshold is reached. Is there any way to have the command fail instantly if there's a container restart/error detected?

<https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/>

Yes, that works to keep the minute usage low by lowering the await times or canceling them all together, but still doesn't address the issue. If you don't wait, a failed deploy will not show up in the pipeline. At the same time, lowering the timeout can create false positives (a database migration running in the init container can take a long time to finish).