To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)
Issue details
When using a targeted destroy of two related resources, such as listener and a target group, both resources are removed from Pulumi's state but only one resources is physically destroyed resulting in an orphaned resource.
Steps to reproduce
Create a load balancer, listener, and target group
Attach the target group tot he listener and listener to the load balancer
Use a targeted destroy for both listener and target group
Expected: Listener and target group should be physically destroyed and removed from the stack's statefile.
Actual: Both are removed from the stack's statefile but only the listener is physically destroyed, resulting in an orphaned target group
Hello!
Issue details
When using a targeted destroy of two related resources, such as listener and a target group, both resources are removed from Pulumi's state but only one resources is physically destroyed resulting in an orphaned resource.
Steps to reproduce
Expected: Listener and target group should be physically destroyed and removed from the stack's statefile. Actual: Both are removed from the stack's statefile but only the listener is physically destroyed, resulting in an orphaned target group
Command:
pulumi destroy -t {target_group_urn} -t {listener_group_urn}
Code: