teardown
Get the latest docs
You are looking at documentation for an older release. Not what you want? Go to the current release documentation.The cfy teardown
command is used to teardown a manager and all resources attached to it.
Note
The teardown process will remove the manager VM and any security groups, ip addresses, key pairs which were provisioned during the bootstrap process. It’s important to note that if you used the simple-manager-blueprint to bootstrap a manager, no resources will be deleted but the manager will become non-functional after tearing it down.
Usage: cfy teardown [options] -f
Teardown a manager.
Required flags
-f, --force
- This flag is mandatory to perform the teardown. Note that if there are running deployments on the manager, the--ignore-deployments
flag must also be passed to perform the teardown.
Optional flags
--ignore-deployments
- Teardown even if there are existing deployments on the manager. Note that ignoring deployments should be used with care as the manager controlling any resources provisioned by it (i.e. running deployments) will not be removed. It will be up to the user to remove those unecessary resources.
Example
$ cfy teardown -f --ignore-deployments
...
Using manager 52.31.106.71 with port 80
2016-06-29 14:11:10 CFY <manager> Starting 'uninstall' workflow execution
2016-06-29 14:11:10 CFY <manager> [sanity_dee2c] Stopping node
2016-06-29 14:11:10 CFY <manager> [webui_ef68c] Stopping node
.
.
.
2016-06-29 14:11:25 CFY <manager> [rest_service_fd6df.stop] Task succeeded 'fabric_plugin.tasks.run_script'
2016-06-29 14:11:26 CFY <manager> [rest_service_fd6df] Deleting node
2016-06-29 14:11:26 CFY <manager> [elasticsearch_8d1cf] Stopping node
2016-06-29 14:11:26 CFY <manager> [rabbitmq_023a2] Stopping node
.
.
.
2016-06-29 14:12:56 LOG <manager> [agents_security_group_c58f4.delete] INFO: Attempted to delete Security Group: sg-2f503548.
2016-06-29 14:12:56 CFY <manager> [agents_security_group_c58f4.delete] Task succeeded 'ec2.securitygroup.delete'
2016-06-29 14:12:56 CFY <manager> 'uninstall' workflow execution succeeded
...