diff options
Diffstat (limited to 'src/main/scripts/forceDeleteTool.sh')
| -rw-r--r-- | src/main/scripts/forceDeleteTool.sh | 29 |
1 files changed, 14 insertions, 15 deletions
diff --git a/src/main/scripts/forceDeleteTool.sh b/src/main/scripts/forceDeleteTool.sh index 2d42fda..f24bacb 100644 --- a/src/main/scripts/forceDeleteTool.sh +++ b/src/main/scripts/forceDeleteTool.sh @@ -1,4 +1,4 @@ -#!/bin/ksh +#!/bin/sh # # ============LICENSE_START======================================================= # org.onap.aai @@ -25,12 +25,12 @@ # forceDeleteTool.sh -- This tool is used to delete nodes that cannot be deleted using # the normal REST API because of internal DB problems. For example, Phantom nodes # and duplicate nodes cause errors to happen in "normal" REST API codes and must -# be deleted using this tool. -# Since it is not using the "normal" REST logic, it is also not invoking the "normal" -# edge rules that we use to cascade deletes to "child" nodes. So - this tool can be dangerous. -# Ie. if you accidently delete a parent node (like a cloud-region) that has many dependent +# be deleted using this tool. +# Since it is not using the "normal" REST logic, it is also not invoking the "normal" +# edge rules that we use to cascade deletes to "child" nodes. So - this tool can be dangerous. +# Ie. if you accidently delete a parent node (like a cloud-region) that has many dependent # child nodes, there will be no way to get to any of those child-nodes after the cloud-region -# has been deleted. +# has been deleted. # There are several environment variables defined in aaiconfig.properties to help minimize errors like that. # aai.forceDel.protected.nt.list=cloud-region # aai.forceDel.protected.edge.count=10 @@ -40,7 +40,7 @@ # # -action (required) valid values: COLLECT_DATA or DELETE_NODE or DELETE_EDGE # -userId (required) must be followed by a userid -# -params4Collect (followed by a string to tell what properties/values to use +# -params4Collect (followed by a string to tell what properties/values to use # as part of a COLLECT_DATA request. Must be in the format # of ?propertName|propValue? use commas to separate if there # are more than one name/value being passed. @@ -49,22 +49,22 @@ # -overRideProtection --- WARNING ? This over-rides the protections we introduced! # It will let you override a protected vertex or vertex that has more # than the allowed number of edges or descendants. -# -DISPLAY_ALL_VIDS (optional) - in the rare case when you want to see the -# vertex-ids (vids) of all the CONNECTED vertices, you can use this. By +# -DISPLAY_ALL_VIDS (optional) - in the rare case when you want to see the +# vertex-ids (vids) of all the CONNECTED vertices, you can use this. By # default, we do not show them. -# -# +# +# # For example: -# +# # forceDeleteTool.sh -action COLLECT_DATA -userId am8383 -params4Collect "tenant-id|junk tenant01 ID 0224" -# +# # forceDeleteTool.sh -action COLLECT_DATA -userId am8383 -params4Collect "cloud-owner|junkTesterCloudOwner 0224,cloud-region-id|junkTesterCloud REgion ID 0224" # # forceDeleteTool.sh -action DELETE_NODE -userId am8383 -vertexId 1234567 # # forceDeleteTool.sh -action DELETE_EDGE -userId am8383 -edgeId 9876543 # -# +# COMMON_ENV_PATH=$( cd "$(dirname "$0")" ; pwd -P ) . ${COMMON_ENV_PATH}/common_functions.sh @@ -74,7 +74,6 @@ start_date; echo " NOTE - if you are deleting data, please run the dataSnapshot.sh script first or " echo " at least make a note the details of the node that you are deleting. " -check_user; source_profile; execute_spring_jar org.onap.aai.dbgen.ForceDeleteTool ${PROJECT_HOME}/resources/forceDelete-logback.xml "$@" |