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

I don't think so. Stacks know which other stacks they depend on; they don't know which stack depend on them.

One option might be to use automation api.

I considered this - I know our guys have made the mistake of nuking a stack that was a dependancy…. not a pretty sight.

Sounds like your permissions are... too permissive :wink:

Stack deletion should require more than a simple PR!

In this case it was someone deleting a portion of their multi stack dev system. 

I know <@UQ8K13T7X> has spoke about getting the service to understand stack references better because it does have a global view of all stacks and so can say "this stack is used by other stacks so don't delete it". Worth raising an ask at <https://github.com/pulumi/pulumi-cloud-requests/issues>

We do have an issue open add the concept of "protected stacks" similar to protected resources: <https://github.com/pulumi/pulumi-cloud-requests/issues/48>

Would you mind giving that a :+1: and adding a comment with any notes you might have?

Pulumi dung has an example of automation api with dependencies.  So stand up stack A and it does B first then A.  Destroy A and it destroys B first with approval prompts of course.  Just automation api running over multiple stacks. <https://github.com/gitfool/Pulumi.Dungeon|https://github.com/gitfool/Pulumi.Dungeon>