There is trash left behind after deepify undeploy

[ddimitrioglo]

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]

@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]

@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.