Skip to content
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

There is trash left behind after deepify undeploy #409

Open
ddimitrioglo opened this issue Aug 18, 2017 · 2 comments
Open

There is trash left behind after deepify undeploy #409

ddimitrioglo opened this issue Aug 18, 2017 · 2 comments
Assignees

Comments

@ddimitrioglo
Copy link

deepify undeploy -r deep-stage-public-9a0244c9

11:42:25 GMT-0400 (EDT) Undeploying "9a0244c9" resources from "stage" environment ...
[REMOVED for summary purposes]
11:42:33 GMT-0400 (EDT) The CloudFront distribution E2ZXWJT71JJDOU is already disabled but not yet deployed. Waiting...
11:42:34 GMT-0400 (EDT) Removing resource #E2ZXWJT71JJDOU from CloudFront
11:42:34 GMT-0400 (EDT) There are 1 resources removed from CloudFront

deepify undeploy -r deep-test-public-df6cece4

11:42:41 GMT-0400 (EDT) Undeploying "df6cece4" resources from "test" environment ...
[REMOVED for summary purposes]
11:42:49 GMT-0400 (EDT) The CloudFront distribution E2HEQ0JQRN6OOD is already disabled but not yet deployed. Waiting...
11:42:49 GMT-0400 (EDT) Removing resource #E2HEQ0JQRN6OOD from CloudFront
11:42:49 GMT-0400 (EDT) There are 1 resources removed from CloudFront
11:42:50 GMT-0400 (EDT) Removing resource #DeepTestAdmindf6cece4 from IAM
11:42:50 GMT-0400 (EDT) Removing resource #DeepTestBackendRoled61fdddddf6cece4 from IAM
11:42:50 GMT-0400 (EDT) There are 2 resources removed from IAM

@ddimitrioglo
Copy link
Author

@eistrati After some investigation I've found out that deepify undeploy leaves garbage due to the error:

Throttling: Rate exceeded

P.S. Details here

@eistrati
Copy link
Contributor

@ddimitrioglo I still recommend prepend "REMOVE FAILED" to CF comment before un-deploying everything, similar to "REMOVE" comment on successful deploy. In case deepify undeploy fails, at least we'll have the capability to observe how often and maybe learn something that will help us improve deepify.

@ivignan ivignan added this to the Milestone #6 - August milestone Aug 21, 2017
@ivignan ivignan modified the milestones: September 2017, Milestone #6 - August Sep 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants