From 94cbaca0f5d9447afe9b0f392f248470420422e5 Mon Sep 17 00:00:00 2001 From: Tommy Carpenter Date: Tue, 22 Aug 2017 17:49:55 -0400 Subject: [DCAEGEN2-74] merge broker deletion plugin to cdap Change-Id: If8fecde180c37ae1332e9ef53b9b2e8b17169cbe Signed-off-by: Tommy Carpenter --- cdap/cdap_types.yaml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'cdap/cdap_types.yaml') diff --git a/cdap/cdap_types.yaml b/cdap/cdap_types.yaml index 497307c..083d011 100755 --- a/cdap/cdap_types.yaml +++ b/cdap/cdap_types.yaml @@ -6,7 +6,7 @@ plugins: cdap_deploy: executor: central_deployment_agent package_name: cdapcloudify - package_version: 14.0.2 + package_version: 14.1.0 data_types: cdap_connections: @@ -88,3 +88,14 @@ node_types: description: "new unbound config for the CDAP AppConfig as a JSON" default: {} + dcae.nodes.broker_deleter: + derived_from: cloudify.nodes.Root + interfaces: + cloudify.interfaces.lifecycle: + delete: #stop better than delete? not sure it matters much. Think all source interfaces are operated on before target on uninstall. + implementation: cdap_deploy.cdapcloudify.cdap_plugin.delete_all_registered_apps + inputs: + connected_broker_dns_name: + type: string + description: This is the broker's DNS name. There could be multiple brokers/clusters at a site. Could by populated via an intrinsic_function in a blueprint, or manually via inputs file + default: "cdap_broker" -- cgit 1.2.3-korg