Repository deletion

Owned by Debesh Roy Chowdhury
Last updated: Jun 03, 2024 by Manas Bajaj
2 min read

Overview

A Syndeia repository cannot be deleted using the Syndeia client if it has any children (containers, artifact types, relation types, and container types). In order to delete a repository and all its children recursively, the repository delete command can be used. This action will trigger a cascading delete starting from the repository (R) whose Syndeia key is provided in the command parameters. It will remove

  • Containers owned by the repo R

  • Artifacts owned by the containers in the repo R

  • Relations owned by the containers in the repo R

  • Container Types, Artifact Types, Relation Types owned by the repo R

  • Relations owned by containers in other repositories (not R), where the source/target of the relation are artifacts in this repo R

This action is irreversible.

Deleting Repository

The delete repository (cascade) can only be run from the Syndeia installation server.

Go to the DevOps installation folder

  1. Login to the server where Syndeia Cloud is installed.

  2. Navigate to the folder $SC_HOME/devops-3.5 (eg. /opt/icx/syndeia-cloud-current/devops-3.5/bin)

Run the delete repository command

  1. Run the command to start the cascading delete of the repository.

./devops -Dsyndeia.client.action=delete -Dsyndeia.delete.repoKey=<repository sKey> -Dsyndeia.client.username=<username> -Dsyndeia.client.password=<password> -Dconfig.file=/opt/icx/syndeia-cloud-current/devops-$SC_snapshot_version/conf/application.conf

where,

repository sKey: the Syndeia key (sKey) of the repository that you want to delete (eg. REPO2, REPO90, REPO57, etc.)

username: Username of the user with delete permissions on all the Syndeia entities - Repository, Container, Artifact, Relation, Artifact Type, Container Type and Relation Type

password: Password for the username provided.

Note, if you have enabled HTTPS only, please ensure you have updated the web-gateway URL in the lagom.services section of the devops' conf/application.conf file beforehand (see Securing Syndeia Cloud for more details)

2. Once the command is run, the Syndeia DevOps client will systematically start deleting the children of the given repository starting from the relations

 

3. On a successful run of the command, the following message will be seen in the console

The repository key of any repository can be retrieved from the Digital Thread Explorer or using the Syndeia Cloud REST APIs

Â