You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 forcf 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
The text was updated successfully, but these errors were encountered: