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

You don't have control over the operation order. Your code builds a graph of resources that Pulumi needs to manage. Pulumi decides what order to build those resources in.

The correct solution here is to import the existing resources so that the `up` works correctly.

I would expect `refresh` to detect them, but it's not

No, refresh looks for differences between code and Pulumi-managed resources. You want to import the resource, to make it a Pulumi-managed resource.

This resource was created by Pulumi and somehow it lost track

Is there a way to ignore a section of non-dependent resources in an update? For example if you have 2 EKS clusters, could you ignore updates to one so the other can have updates processed?

No. You can apply an update to just one group of resources by specifying all their URNs on the command line.

Projects are functional groupings of resources. If you have two groups of resources that you want to update independently, you must have two projects.

Thank you, the target command line helped so much