Both "environments" are being undeployed when application hash was used as option

[avozicov]

Pre-requisites:

• there should the a case to fail the deploy execution, (for e.x. missing required application build directories)

Steps to reproduce:

• Navigate to app "X" src directory
• Configure "deeploy.json" file and set stage value for "env" key
• Deploy app "X" to your aws account and wait to succeed
• Configure "deeploy.json" file and set dev value for "env" key
• Perform deploy which is required to fail for reproduce the issue
• Answer "Y" when prompt to undeploy resource by application hash
• Let the undeploy process finish

BUG:

• Both stage and dev environments are being undeployed when application hash was used as undeploy option without specified environment

• This issue can be critical for the case when prod environment was successful deployed and dev environment was failed on next deploy, as a result - user can accidentally remove production environment from his account without any warning before submitting undeploy option

Note:

• After discussing with developers this seems to be an old issue not introduced with "deepify list" implementation

Please refer to attachment for more details:

[mgoria]

This issue is caused by excluding application env from app hash (this change was done while implementing blue/green as a request from @eistrati if I'm not mistaken) and deepify related functionality list, undeploy, etc, was not adjusted to these changes, so deepify undeploy removes everything that matches provided hash without looking at resource env.