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

Is a child resource necessarily dependent on the parent resource? Maybe add an explicit _dependsOn_ and see if that helps?

If there's no property in the child resource that refers back to a property of the parent resource, then maybe `--target-dependents` won't notice...

A child isn’t a “dependent” technically. “dependent” relationships are defined by `dependsOn` and would be destroyed by `--target-dependents`.

Parent-child relationships are defined by the `parent` property and/or `componentResources`

I do find it odd though, the docs for `--target` say
```All resources necessary to destroy this target will also be destroyed.```
I would expect that to mean that it would destroy the child.

I expect <@U012UJTT55M> is right on the money here though as to why that happens

Thanks <@U012UJTT55M> <@U01038HJ93R> - for now I think easiest solution is to define each resource individually with its own `--target`  flag. Thanks for the help

I guess you don't have too many resources :slightly_smiling_face: A dependsOn added to the opts of everything that has a parent opt would be first choice! :slightly_smiling_face:

This issue covers what we’ve discussed: <https://github.com/pulumi/pulumi/issues/5870> - feel free to upvote/comment as that helps with prioritizing