Load Balancer Problem with Pre-Existing Target Group about fargatecli HOT 4 OPEN

Looks like you've found a bug. There's a bit of awkwardness with the order of creation and deletion of load balancers and services, and it looks like I blew it in this scenario. 🤬

To delete the vestigial target group, you can run:

aws elbv2 delete-target-group --target-group-arn `aws elbv2 describe-target-groups --names testapp-default --query TargetGroups[].TargetGroupArn --output text`

This command will find the ARN of the errant target group and delete it.

The scenario you pose above is really my target use case. A 1:1 mapping is not required. It's just a matter of creating a load balancer listening on HTTPS and a service listening on port 8080. Let me know if I can help you further get this running! I'm leaving this issue open to investigate this target group business, and I suspect it's related to #9.

from fargatecli.

Hey that did the trick, thanks! Everything is running perfectly now, your project is extremely helpful!

from fargatecli.

Root cause: Destroy needs to delete all load balancer listeners before destroying the target group.

from fargatecli.

Is this bug somehow scheduled to get fixed in any release? In which release we can expect the fix?

from fargatecli.