Project and repo deletion actually do not delete the db spaces + repos, and do not free disk space about gitness HOT 1 CLOSED

Hi @ignaciolg
The reason we don't immediately delete space/repos from disk is to support restore for a specific period of time (as accidental deletion happens!). Currently, there's a job that will wipe out old deleted space/repos after 90 days from the deletion time.

You can set this configuration via GITNESS_REPOS_DELETED_RETENTION_TIME="1s" , the default is "2160h" (or 90 days)

If you'd like to completely delete space/repos there's a purge API that you can use as follow:

• Purge soft deleted repos:
  POST {{baseUrl}}/api/v1/repos/{repo-ref}/purge?deleted_at={exact repo deletion time}
  -- repo-ref can be "parent-space/repo-identifier" or repo_id (both works)
  -- deleted_at: you can fetch this value from db (table repos) (the second to last column in your screenshot)

• Purge soft deleted spaces:
  POST {{baseUrl}}/api/v1/spaces/{space-ref}/+/purge?deleted_at={exact space deletion time}
  -- space-ref can be "space-identifier" or "space_id" (both works)
  -- deleted_at: you can fetch this value from db (table spaces)

For your convenient, the (soft) delete API returns the deleted_at timestamp, if you'd like to use it right away for future and not query db.

About UI listing deleted spaces, it's a caching issue that I'll discuss with our front-end team. cc: @rkapoor10

Hope this helps!

from gitness.