Description
Someone administrating an MTA might not always know what entities were created during the cf deploy. In particular, he might not know if there are service instances or service brokers created.
Thus, it's proposed to have a --delete-all option for cf undeploy to get rid of everything that was created during cf deploy. Thus, so he can be sure that no manual cleanup is necessary afterwards.
Expected behavior
The --delete-all option should act the same as providing --delete-services --delete-service-brokers to the undeploy command.
An example usage would be:
cf undeploy my.example.mta --delete-all
Internal Tracking Number:
LMCROSSITXSADEPLOY-546
Description
Someone administrating an MTA might not always know what entities were created during the cf deploy. In particular, he might not know if there are service instances or service brokers created.
Thus, it's proposed to have a
--delete-alloption forcf undeployto get rid of everything that was created during cf deploy. Thus, so he can be sure that no manual cleanup is necessary afterwards.Expected behavior
The
--delete-alloption should act the same as providing--delete-services --delete-service-brokersto the undeploy command.An example usage would be:
cf undeploy my.example.mta --delete-allInternal Tracking Number:
LMCROSSITXSADEPLOY-546