Take in account services' dependencies during undeploy

[corporateuser]

Description

Currently there is no sequence of deleting services during cf undeploy command. So we have situations like:

1. HANA Cloud deleted before service manager
2. SaaS service deleted before HTML5 repo service
   Such situations create unexpected situations for corresponding service brokers.

It would be good:

1. Check if there are any subscriptions existing for the services existing in MTA
2. Delete services in sequence opposite to its creation, so if service manager is requiring Hana Cloud we should first ensure that service manager to be deleted first and Hana Cloud will be deleted after that.

[theghost5800]

Hi @corporateuser , yes you are right, currently there is no order in deletion of service instances. Up until now we didn't expect any order to be required during deletion of any mta modules or resources.

I would like to understand what does it mean the following sentence "subscriptions existing for the services existing in MTA" from CF perspective? Does it mean existing service keys or service bindings between some application?