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

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.