Closed eistrati closed 7 years ago
Here is another one:
MitocGroup:~ eugene$ deepify list
14:24:19 GMT-0400 (EDT) To get more details, run deepify list --depth=2 or deepify list --depth=3
#1. ATM Api (ebf6f3ce) | using 11 cloud services
--------------------------------------------
#2. ATM Consolidated (3e4186ab) | using 11 cloud services
-----------------------------------------------------
#3. My Custom Web App 02db236e7d78a427e226469b921c09e1 (9d71cad5) | using 11 cloud services
---------------------------------------------------------------------------------------
#4. My Custom Web App 29ed7db20fed59212082cefe53ae629e (1558a2a9) | using 11 cloud services
---------------------------------------------------------------------------------------
#5. dev (430f1fff) | using 1 cloud services
---------------------------------------
#6. hello.deep.mg (370b9c50) | using 10 cloud services
--------------------------------------------------
#7. todo.deep.mg (55182282) | using 11 cloud services
-------------------------------------------------
#8. unknown application | using 2 cloud services
--------------------------------------------
#9. www.adtechmedia.io (57ad5dd8) | using 12 cloud services
-------------------------------------------------------
#10. www.deep.mg (41ae5689) | using 9 cloud services
-----------------------------------------------
#11. www2_serverlessConf (7bb794bc) | using 11 cloud services
--------------------------------------------------------
MitocGroup:~ eugene$ deepify list -r 430f1fff -d 3
14:24:46 GMT-0400 (EDT)
#1. dev (430f1fff) | using 1 cloud services
---------------------------------------
1. Security Tier / Amazon IAM | using 33 cloud resources:
1.1. DeepDevAdmin430f1fff
1.2. DeepDevAdminRole1d3d2efc430f1fff
1.3. DeepDevAdminRole3242d1c0430f1fff
1.4. DeepDevAdminRole33266741430f1fff
1.5. DeepDevAdminRole498cabb1430f1fff
1.6. DeepDevAdminRole8125e59f430f1fff
1.7. DeepDevAdminRole8bb0a8d8430f1fff
1.8. DeepDevAdminRole997475c6430f1fff
1.9. DeepDevAdminRolea0f89290430f1fff
1.10. DeepDevAdminRoledbbaf089430f1fff
1.11. DeepDevAdminRoledd4228b1430f1fff
1.12. DeepDevAdminRoleeb84d5da430f1fff
1.13. DeepDevAdminRolefe5785b7430f1fff
1.14. DeepDevBackendRole1d3d2efc430f1fff
1.15. DeepDevBackendRole3242d1c0430f1fff
1.16. DeepDevBackendRole33266741430f1fff
1.17. DeepDevBackendRole498cabb1430f1fff
1.18. DeepDevBackendRole8125e59f430f1fff
1.19. DeepDevBackendRole8bb0a8d8430f1fff
1.20. DeepDevBackendRole997475c6430f1fff
1.21. DeepDevBackendRolea0f89290430f1fff
1.22. DeepDevBackendRoledbbaf089430f1fff
1.23. DeepDevBackendRoledd4228b1430f1fff
1.24. DeepDevBackendRoleeb84d5da430f1fff
1.25. DeepDevBackendRolefae68c1c430f1fff
1.26. DeepDevBackendRolefe5785b7430f1fff
1.27. DeepDevFfhgfhfghfgh430f1fff
1.28. DeepDevFfhgfhfghfghghgfhfghgfh430f1fff
1.29. DeepDevTestDuplicate430f1fff
1.30. DeepDevTesting_role430f1fff
1.31. DeepDevTestRole123456789430f1fff
1.32. DeepDevTestRole430f1fff
1.33. DeepDevTest_mobile430f1fff
Test Passed Acceptance Criteria:
Status Update: I have found an use case in which bug is still reproduced, please refer to the steps bellow:
deepify undeploy --dirty
deepify list --depth=3
BUG: There are still resources left after undeploy process is completed
1. Data Tier / Amazon CloudWatchLogs | using 1 cloud resources:
1.1. /aws/lambda/DeepDevDdbEventualConsistencyListenQueues357e03be8a
Note:
deepify undeploy -r _application hash_
Please refer to attachments for more details:
Please refer bellow for the "deepify undeploy" related issue https://github.com/MitocGroup/deepify/issues/388
Test Failed
Please refer to attachments for more details:
1.Deployed test application
1.Listed provisioned services for deployed application
_2.Performed "deepify undeploy by [apphash] option" 2.1 Listed provisioned services after undeploy
3. Reviewed "undeploy log" 3.1 Checked "CloudWatch logs" from aws console
4. Listed provisioned services once again - Cloudwatch logs are listed as provisioned services
Note:
This issue with CloudWatchLogs seems to be generated only for cloud watch logs related to scheduled lambdas, that's why on undeploying it tells logs are removed successfully but on successive deepify list
some log groups are still listed, these log groups sometimes are created again by scheduled lambdas that weren't removed yet. Looking for a solution ...
Test Passed
I had to clean up our AWS account earlier today because of some CloudWatch resources that haven't been removed by
deepify undeploy
. Here below is my log: