Hi, Im thinking, what about stop wait for long tasks, like aws eks creation, aws cli take like 40 mins to finish while Pulumi only waits

Why do you want to see if the resource is created? The Pulumi app won't finish until the creation completes.

I trigger cluster creation tasks on a worker that sits waiting for 40 minutes without doing anything but waiting. I just want to save execution time

It doesn't sound like a Pulumi problem. If AWS is taking a long time, then there's nothing Pulumi can do. Perhaps there's some options on the resource that makes it smaller or faster? You may benefit from splitting your project. If the slow stuff only needs to happen once, then have it in one project, and the more frequently deployed resources can be in another.

I think that on the Pulumi side, the creation of a resource can be made idempotent. Then, when retrying the creation, if the object already exists or is being created, Pulumi updates its status.

> the creation of a resource can be made idempotent. Pulumi uses a declarative model, setting up a desired state. It isn't possible to tell Pulumi to "create" a resource, only to tell it to ensure that the resource exists. While idempotency might not be guaranteed (since Pulumi is limited by the APIs it calls), there is no need to "make" the creation of a resource one thing or another thing. This is Pulumi's responsibility. You just need to declare what you want the resource to look like, and Pulumi will sort the rest.