Unexpected Behavior: I realized settings the parent and deletedBy can be really useful when you want to destroy or update a resource, so I decided to set them, however when I do this for every resource, the pulumi try to replace it by creating new resource and deleting old one, but I just changed the parent and deletedBy, and as I did not changed any resource parameter, I expect do not replace that.

When changing the parent, you'll also need to set up an alias so pulumi knows where to move state to

Thanks @dry-keyboard-94795 useful information also if I set parent for a resource, does pulumi skip delete of child resource when deleted parent? or I have to explicitly set deletedWith?

alias

is a ResourceOptions config. Guide on usage here: https://www.pulumi.com/blog/cumundi-guest-post/

Sorry, I did not understood, if I set the

parent

in the child resource option, does pulumi skip deleting child when deleted parent?

nope, you also need to set

deletedWith

I see

possibly, those should have deleted

😭😭

If you do a pulumi refresh, do they show up in the stack again?

no

Does the

role

have

deletedWith=instance

or something like that?

yes, the role has

deletedWith=instance

nice. I'm surprised

deletedWith

gets inherited this way

I am surprised too 😄

feature was implemented here, worth commenting on it with your unexpected behaviour: https://github.com/pulumi/pulumi/issues/12158 Though Frassle has already mentioned this limitation

Yes, I see, thank you for explanation