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've never been able to figure this one.. have always had to do this manually :disappointed:

It works for a single resource, but if that resource has dependencies... ¯\_(ツ)_/¯

I wonder if a potential solution is to remove the paralellism? I.e. pulumi up -parallel 1 ?

I think it's not even trying to replace the dependent resource, iirc.

For me this is the case:
• AWS LoadBalancer TargetGroup definition. Replace because of property change.
• AWS LoadBalancer TargetGroupAttachment (creation because I just added it to the script) 

So in this case, I've always had to comment out the target group and attachment, to destroy them; then uncomment them to create them with the correct TG properties

Oof. What if I try to “get” the targetGroup after defining it using an await?

The approach you had to take is making me angry :stuck_out_tongue:

I don't understand your idea? I don't think getting something from a resource will help control when it gets deleted / recreated.. :confused:

Something must be different about the resource when it gets deleted recreated… if you could somehow test against that difference…

The problem is not knowing the property that has caused it to changed.

Although I imagine the arn will have changed…

Unless Pulumi provides an `isDirty()` property or similar, I don't think it's feasible to tell if a resource will be deleted.

I have been treating this as a Pulumi bug / unimplemented feature, and have been working around it. I haven't been able to come up with an in-code workaround.

So this worked: `pulumi up -p 1` which essentially makes it non parallel, i.e. it only performs one action at a time.

I hope I remember that next time it happens...

It’s not ideal since it makes everything mucho slow

I don't get how it happens though, since it should be creating all the resources before deleting others, so there should be a conflict.. but far be it from me to complain about it :slightly_smiling_face: