Can I force a dependency on a replacement I have an issue wh

Question

Can I force a dependency on a replacement I have an issue where a dependent item is being created before the item it is dependent on being replaced I tried the dependsOn listenerOption but it doesn t seem to work

little-cartoon-10569 · Answer

I ve never been able to figure this one have always had to do this manually disappointed

damp-painting-47843 · Answer

Ouch

little-cartoon-10569 · Answer

It works for a single resource but if that resource has dependencies ツ

damp-painting-47843 · Answer

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

little-cartoon-10569 · Answer

Try it but I m not optimistic

little-cartoon-10569 · Answer

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

damp-painting-47843 · Answer

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

little-cartoon-10569 · Answer

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

damp-painting-47843 · Answer

Oof What if I try to get the targetGroup after defining it using an await

damp-painting-47843 · Answer

I m going to try that and see

damp-painting-47843 · Answer

The approach you had to take is making me angry stuck out tongue

damp-painting-47843 · Answer

Or pulumi all maybe

little-cartoon-10569 · Answer

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

damp-painting-47843 · Answer

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

damp-painting-47843 · Answer

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

damp-painting-47843 · Answer

Although I imagine the arn will have changed

damp-painting-47843 · Answer

This is hurting my brain

little-cartoon-10569 · Answer

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

little-cartoon-10569 · Answer

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

damp-painting-47843 · Answer

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

little-cartoon-10569 · Answer

Niiiice

little-cartoon-10569 · Answer

I hope I remember that next time it happens

damp-painting-47843 · Answer

It s not ideal since it makes everything mucho slow

little-cartoon-10569 · Answer

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