This message was deleted.

sparse-intern-71089

05/05/2021, 2:26 AM

This message was deleted.

little-cartoon-10569

05/05/2021, 2:27 AM

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

little-cartoon-10569

05/05/2021, 2:28 AM

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...

➕ 1

red-match-15116

05/05/2021, 2:48 AM

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

red-match-15116

05/05/2021, 2:51 AM

I do find it odd though, the docs for

--target

say

Copy code

All resources necessary to destroy this target will also be destroyed.

I would expect that to mean that it would destroy the child.

red-match-15116

05/05/2021, 3:03 AM

I expect @little-cartoon-10569 is right on the money here though as to why that happens

quaint-air-36266

05/05/2021, 3:22 AM

Thanks @little-cartoon-10569 @red-match-15116 - for now I think easiest solution is to define each resource individually with its own

--target

flag. Thanks for the help

little-cartoon-10569

05/05/2021, 3:23 AM

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

👍 1

red-match-15116

05/05/2021, 3:25 AM

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

Open in Slack

Previous Next

Pulumi Community

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.