...
This action is irreversible.
Prerequisites
The user performing the deletion must be
super.user
If you have enabled HTTPS only, please ensure you have updated the
web-gateway
URL to the server FQDN in thelagom.services
section of the devops'conf/application.conf
file beforehand (see step 10 of Securing Syndeia Cloud for more details)
Deleting Repository
The delete repository (cascade) can only be run from the Syndeia installation server.
...
Login to the server where Syndeia Cloud is installed.
Navigate to the folder
$SC_HOME/devops-3.56/bin
(eg./opt/icx/syndeia-cloud-current/devops-3.56/bin
)
Run the delete repository command
Run the command to start the cascading delete of the repository, where
$SC_snapshot_version
= the version of SC you are running.
./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
...
password: Password for the username provided.
...
.
...
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
...
:
Code Block | ||
---|---|---|
| ||
[info] com.intercax.syndeia.api.RepositoryApi(] - Deleting repository with key REPO3
[info] com.intercax.syndeia.delete.CloudDeleteAction[] delete repository action is successful |
Info |
---|
The repository key of any repository can be retrieved from the Digital Thread Explorer or using the Syndeia Cloud REST APIs |
...