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

So I have the following, we recreate a k8s cluster in a parent stack (because many changes require that). Cluster gets replaced, all is good. However a child stack (a separate pulumi run) that depends on this cluster (and created resources in it) will keep thinking it has many resources deployed in a cluster that's now deleted.

This means the provider already fails to connect, breaking the state of the child stack quite severely.

<@UB3BGTV63> any advice on how to keep stacks in sync?

How do you even express dependencies like this. some parent stack deleting everything that roots child stack resources (at runtime)

it would be very helpful to have an easy way of removing everything depending on a specific provider id as a temporary measure