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

Hi everyone! Is it possible to prevent one stack from getting destroyed as long as another stack is up? E.g. I have stack A which creates an EKS cluster and stack B for creating k8s resources in the cluster. Destroying stack A when stack B is still up leaves that stack in a bad state. And more worse, there may be unattended resources left that are not under Pulumi's control at all, e.g. load balancers that have been created by the load balancer manager.
Can stack B register itself in stack A so that stack A can't be destroyed until stack B deregisters itself on its own destruction?

Not out of the box. You can make specific resources  safe from destroyed by setting the _protect_ opt to true, but that's it.

You could write a dynamic provider that adds the _protect_ opt to every resource based on a stack export from another stack...

That would require you to _up_ your stack A before _and_ after stack B.. but it would work (I think).

Another option would be to wrap your stack-A Pulumi program in automation-api, which checks for stack B and prevents deletes. That would be much easier.