https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
l
I've never been able to figure this one.. have always had to do this manually šŸ˜ž
d
Ouch.
l
It works for a single resource, but if that resource has dependencies... ĀÆ\_(惄)_/ĀÆ
d
I wonder if a potential solution is to remove the paralellism? I.e. pulumi up -parallel 1 ?
l
Try it, but I'm not optimistic...
I think it's not even trying to replace the dependent resource, iirc.
d
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)
l
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
d
Oof. What if I try to ā€œgetā€ the targetGroup after defining it using an await?
Iā€™m going to try that and see.
The approach you had to take is making me angry šŸ˜›
Or pulumi.all maybeā€¦
l
I don't understand your idea? I don't think getting something from a resource will help control when it gets deleted / recreated.. šŸ˜•
d
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ā€¦
This is hurting my brain.
l
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.
d
So this worked: 
pulumi up -p 1
which essentially makes it non parallel, i.e. it only performs one action at a time.
l
Niiiice.
I hope I remember that next time it happens...
d
Itā€™s not ideal since it makes everything mucho slow
l
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 šŸ™‚
Open in Slack
PreviousNext
Powered by

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.

Powered by