The correct way to remove an application from the fabric is to deploy and application xml file that is empty. This will replace your existing application with one that does not contain any flows, tasks, etc...
For example:
<?xml version='1.0'?>
<!DOCTYPE app SYSTEM 'FabricApp.dtd'>
<app name='test_app' version='1.1'>
</app>
This ensures that the application will stay "removed" if it is removed.
For example, if a worker with an old version of this application came online and joined that fabric again, that empty app xml will override any old application because the empty app xml has a higher version.
We do plan on adding additional functionality later, but for now this is how you should remove a fabric application.
The correct way to remove an application from the fabric is to deploy and application xml file that is empty. This will replace your existing application with one that does not contain any flows, tasks, etc...
For example:
This ensures that the application will stay "removed" if it is removed.
For example, if a worker with an old version of this application came online and joined that fabric again, that empty app xml will override any old application because the empty app xml has a higher version.
We do plan on adding additional functionality later, but for now this is how you should remove a fabric application.
OK. That works for me.