-
Notifications
You must be signed in to change notification settings - Fork 13
fix(aws): surface NLB errors instead of swallowing them #645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -102,7 +102,7 @@ func (p *Provider) delete(cache *AWS) error { | |
| // But we can also store it in status.Cluster properties | ||
| // Actually, let's check if we can get it from the environment status | ||
| if err := p.deleteNLBForCluster(clusterCache); err != nil { | ||
| p.log.Warning("Error deleting load balancer: %v", err) | ||
| return fmt.Errorf("failed to delete load balancer (resources may be leaked): %w", err) | ||
| } | ||
|
Comment on lines
104
to
106
|
||
| } | ||
| } | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Returning immediately on load balancer deletion failure stops the rest of the teardown (EC2 instances, security groups, VPC). This can leak more resources than just the NLB. Consider continuing with phases 1–3 and returning an aggregated error at the end (or track the NLB error and return it after other cleanup completes).