Task: Delete a Project with a Shell Script

• Permissions Required
• Other Requirements
• The Deletion Script
• Using the Script
• Modifying the Script
• Writing Other Scripts
• Links

Permissions Required

The script requires that special user Anonymous has the following permissions for the project P and its analyses.

• ANALYSIS_DELETE a for all analyses a of P.
• PROJECT_DELETE P

If you will be extending the script to derive the project ID from an analysis directory for some analysis A of the project, you will also need the following permissions for A.

• ANALYSIS_READ A

See Modifying the Script for information on modifying the script to specify credentials for a non-Anonymous user with the required permissions.

Other Requirements

Use the cURL shipped with CodeSonar: $CSONAR/third-party/curl/inst/bin/curl, where $CSONAR is the CodeSonar installation directory. Either:

• add $CSONAR/third-party/curl/inst/bin/ to the front of your PATH,
  or
• edit the script so that the definition of del_project() specifies the full path to $CSONAR/third-party/curl/inst/bin/curl.

The Deletion Script

The following script will delete

• the project whose project ID matches the second argument passed to the script,
• on the hub specified in the first argument to the script.

#! /bin/sh -e


if [ $# -ne 2 ]; then
    echo "Usage: $0 HUB PROJECT_ID"
    exit 1
fi

HUB=$1
PROJECT_ID=$2
CURL_CMD=curl

del_project(){
   "$CURL_CMD" -L --cookie-jar cookies.txt -d remove_project_id="$1" "$2"
}

del_project "${PROJECT_ID}" "${HUB}"

This shell script uses an HTTP POST request to perform the deletion: the POST request is for the hub Home page and must specify remove_project_id=pid, where pid is the project ID of the project to be deleted. It outputs the HTML landing page that reports successful deletion.

The hub functionality for deleting an analysis entails several HTTP redirects across a single session. When you are using an anonymous session, as here, it must be tracked using cookies. The script uses cURL options to ensure that the redirects and cookies are properly accounted for:

• -L instructs cURL to follow redirects.
• --cookie-jar cookies.txt instructs cURL to use local file cookies.txt to manage any cookies involved in completing the command.
  File cookies.txt will be created in your working directory, if it does not already exist.

Inspect the HTML source for a Project page to see the remove_project_form element and how its attributes and sub-elements correspond to the HTTP POST request constructed by the script.

Using the Script

To use this script with your hub, do the following.

1. Copy delete_project.sh to a suitable directory. The remainder of these instructions will refer to this directory as rundir.

   Make sure you have full file permissions in rundir, and that using file rundir/cookies.txt to manage cookies for this task will not cause conflicts with other uses of rundir. If there is a problem, either:

   • select a different rundir, or
   • edit the script to specify a different file name with --cookie-jar.
2. Run the script:
   cd rundir
   ./delete_project.sh protocol://host:port pid
   where

   protocol	is the protocol for your hub: http or https.
   host:port	is the location of your hub.
   pid	is the project ID for the project whose name you wish to change. You can find the project ID: in the GUI Project page URL, which will be of the form http://hub_location/project/project_id.html, or by deriving it based on the analysis ID from the most recent analysis of the project, which in turn is available: in the URL specified at the end build/analysis command output, which will be of the form http://hub_location/analysis/analysis_id.html, or by running the following command, where path/to/projname.prj_files/ is the analysis directory codesonar analysis_id.py path/to/projname.prj_files/ or in file path/to/projname.prj_files/aid.txt, where path/to/projname.prj_files/ is the analysis directory. For details, see Derive the project ID from the analysis directory, below.

   The script will output information about its progress.
3. Attempt to open the project page protocol://host:port/project/pid.html in your web browser to confirm that the project is no longer available.

Invocation Example

Using the hub at http://[::1]:7341, delete the project with ID 3:

Troubleshooting

del_project(){
   "$CURL_CMD" -v -L --cookie-jar cookies.txt -d remove_project_id="$1" "$2"
}

del_project(){
  "$CURL_CMD" -k -L --cookie-jar cookies.txt -d remove_project_id="$1" "$2"
}

Modifying the Script

You may wish to make one or more of the following modifications.

• Stop printing the resulting HTML file to output
• Derive the project ID from the analysis directory
• Provide credentials for a non-Anonymous user

Stop printing the resulting HTML file to output

If you don't want to see the final HTML file notifying you of successful deletion as part of your script's output, you can redirect it to the null location by modifying your curl command. Note that if you make further changes that you need to debug later, you may wish to lift this suppression at least temporarily.

1. Edit delete_project.sh so that curl is invoked with the -o flag and a suitable value.

   del_project(){
      "$CURL_CMD" -o /dev/null -L --cookie-jar cookies.txt -d remove_project_id="$1" "$2"
   }

Derive the project ID from the analysis directory

Instead of specifying the project ID on the command line, you can change the script to read the analysis directory from the command line and derive the project ID by reading the most recent analysis ID from the analysis directory, requesting the corresponding Analysis page from the hub, then reading the project ID from the Analysis page.

Because this approach requires the Analysis page for the analysis A in question, you must have the following permissions for A in addition to the required project permissions.

• ANALYSIS_READ A

Once you have verified that you have these permissions, proceed as follows.

1. Edit delete_project.sh so that the line setting ANALYSIS_ID is replaced with three lines:

   ANALYSIS_DIR=$2
   CSONAR_CMD=codesonar
   ANALYSIS_ID=$("$CSONAR_CMD" analysis_id.py "$ANALYSIS_DIR" | tr -d '\r')
   

   If it is not in your PATH, adjust the setting of CSONAR_CMD to include the full path to your codesonar executable.
2. Delete the line setting PROJECT_HTML_URL and replace it with the following line setting ANALYSIS_HTML_URL.

   ANALYSIS_HTML_URL="${HUB}/analysis/${ANALYSIS_ID}.html"

3. Insert the following code before the definition of del_project(). This new function downloads a page, searches it for the first occurrence of a partial Project page URL, then extracts the ID from the URL.

   get_project_id(){
       PROJ_ID=$("$CURL_CMD" "$2" \
                   | sed -n '/href="\/project\//p' \
                   | head -n1 \
                   | sed 's/.* href="\/project\/\([0-9]*\)\.html".*/\1/')
       # exit with an error if no Project ID found
       if test "${PROJ_ID}" = ""
       then
           echo "No Project ID found."
           echo "This probably means you do not have ANALYSIS_READ permission"
           echo "for the analysis and so cannot access $2."
           exit 1
       else
           eval "$1='${PROJ_ID}'"
       fi
   } 

4. Insert the following code as the second to last line of the script (that is, the line before the del_project invocation). This calls the new get_project_id() function to derive the required Project ID and write it into the PROJECT_ID variable.

   get_project_id PROJECT_ID "${ANALYSIS_HTML_URL}" 

5. When you invoke the script, specify the analysis directory as the second argument.

   For example: using the hub at http://[::1]:7341, delete the analysis whose analysis directory is /myprojects/projectX.prj_files/.

   ./delete_project.sh http://[::1]:7341 /myprojects/projectX.prj_files/

Provide credentials for a non-Anonymous user

If your hub is configured so that special user Anonymous does not have the required permissions, you will need to edit the script to submit credentials for a suitable hub user account.

See CodeSonar HTTP API: Authentication for more information on authentication strategies.

Links

• Typical CodeSonar Tasks
• HTTP API Documentation
• The CodeSonar Hub
• CodeSonar GUI Reference