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

hmm. that kinda kills the ability to use StackReference to break up the infrastructure. I need to share the kubeconfig.

Is there any way to destroy a stack without destroying the items it imported? (I was able to my stacks up so that a second stack imported the ids of the first stack, but then destroying the second stack also destroys the imported resources. )

`import` means take ownership of. 

If you just want to reference existing resources without taking ownership, you can use `.get(id)`. 

ah. I missed that. I think maybe I need to take time to read the whole API instead of skimming :slightly_smiling_face:

You can certainly remove a stack without removing the resources

I believe it’s `pulumi stack rm -f stack`

I have #1 stack that deploys the cluster, and then stack #2 that deploys one of the apps to the cluster. I was trying to destroy the app without destroying the cluster.

Yeah, you definitely need to use a StackReference then. If you need to fix it for now, you can export the stack, remove the resources, then import the stack.