Open mlqn opened 6 months ago
This is a bit of a dangerous path, as the interface in Gitea gives no indication/status as to whether an app is deployed. It would be very easy to accidentally delete a repo, and with that also remove a critical app from production.
Should we look into some other alternatives here? Is there any way to f.ex. disable repo delete in Gitea? Or at the very least limit that options only to a very limited number of people. And instead offer the option to delete repos in the designer interface. That way we can have much more control over when it is OK to delete an app. F.ex.:
Description
Deleting a repository in Gitea should result in the deletion of all associated data.
Here is a non-exhaustive list of data that are not deleted :
A possible solution could be to add a new endpoint to our API that decommissions apps and cleans up all data, and then call this endpoint via webhooks when deleting the repository in Gitea
Additional Information
No response