Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

waypoint destroy on ECS does not delete all AWS resources created by waypoint #805

Closed
aruntomar opened this issue Nov 16, 2020 · 5 comments
Labels
bug Something isn't working plugin/aws
Milestone

Comments

@aruntomar
Copy link

Describe the bug
waypoint up on ECS creates lot of AWS resources eg: ALB, security groups, iam role, ECS cluster, task & execution role, etc
waypoint destroy only destroys the ECS cluster & task definition, leaving behind ALB, security groups, iam roles etc.

Steps to Reproduce
https://github.com/hashicorp/waypoint-examples/blob/main/aws-ecs/nodejs/waypoint.hcl

Expected behavior
I would expect all the AWS resources created by waypoint to be destroyed when waypoint destroy is executed.

@mitchellh mitchellh added bug Something isn't working plugin/aws labels Nov 16, 2020
@krantzinator krantzinator added this to the 0.2.x milestone Dec 16, 2020
@krantzinator krantzinator self-assigned this Jan 19, 2021
@krantzinator krantzinator removed their assignment Mar 26, 2021
@krantzinator krantzinator modified the milestones: 0.2.x, 0.3.x Mar 26, 2021
@ghost
Copy link

ghost commented Apr 10, 2021

It's any update about it? I'm having the same issue, I need to go manually to destroy later the ALB, SGs and other stuff on AWS after I run the destroy command.

@krantzinator
Copy link
Contributor

We plan to address this in an upcoming release.

@evanphx evanphx modified the milestones: 0.4.x, 0.5.x Jun 16, 2021
@wesky93
Copy link

wesky93 commented Jun 26, 2021

In my case, even the ECS cluster and task have not been deleted.

@richstokes
Copy link

Same issue here, is there any way to tell it to clean up all resources?

@briancain
Copy link
Member

Hey there everyone, since this issue has been opened, we've introduced a new concept within Waypoints plugin system called Resource Manager. Now with the most recent version of Waypoint, the plugin should be cleaning up the resources it creates.

For now, I'm going to go ahead and close this issue. If there's a specific resource that seems to be left behind, please open a new issue and we can address fixing that. Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working plugin/aws
Projects
None yet
Development

No branches or pull requests

7 participants