[Enhancement]: See and manage DB backups via API

[DanielHemmati]

Changes

• Add backup configuration to GET /databases API including weather backups are configured locally or via s3 bucket, cron schedule and last successful backup timestamp
• The ability to get the list of backups with detail for a database by using GET /databases/:uuid/backups
• Enhance PATCH /databases/:uuid API. Right now you can configure all of the backup detail you see in the backup panel, including creating a backup, all via api.
• Add the ability to delete a specific backup weather from s3 or locally DELETE /databases/:uuid/backups/:backup_id

I also recorded a video showing a demo: https://www.youtube.com/watch?v=hbN-ygTPBRc
Also I wrote a python script show casing how it can be used via API: https://github.com/DanielHemmati/coolify-api-demo

Issues

• fix [Enhancement]: See and manage DB backups via API #5672

/claim #5672

[DanielHemmati]

Hi @andrasbacsai,

I noticed the PR was closed without being merged, and the branch was deleted. I’d really appreciate a bit of feedback if possible, was there something wrong with the implementation, or was the feature no longer needed?

Understanding what went wrong would help me improve for future contributions. Thanks a lot!

[andrasbacsai]

It was a mistake, sorry. I recreated the next branch and it auto-closed this PR.

[andrasbacsai]

Thanks for the PR and the video! Enjoyed reviewing it.

I found a few things that needs to be fixed:

1. PATCH /databases/:uuid updates the first backup only. This should only update the database related things.
2. PATCH /databases/:uuid/backups/:backup_id this does not exists but should be. This should update the backup related configurations.

Can you please modify the code accordingly?

[DanielHemmati]

Hi @andrasbacsai, Thanks a lot for the feedback!

Just to confirm:
I'll have to undo the logic in PATCH /databases/:uuid so that it only updates the database-related fields.

Then I'll introduce a new route:
PATCH /databases/:uuid/backups/:backup_id, which will specifically handle updates to individual backup configurations.
This will allow users to modify the settings for each backup independently.

[DanielHemmati]

Hey @andrasbacsai, here are the changes i have done right now.

1. Separated backup config logic:
   Moved all backup configuration logic from the update_by_uuid method into a new method called update_backup_config_by_uuid_and_backup_id. Now, update_by_uuid is focused solely on updating the database configuration.

2. Removed backup creation logic:
   Since the route PATCH /database/<db-uuid>/backups/<backup_id> implies an update to an existing backup, it no longer supports backup creation. If needed, I can introduce a separate route specifically for creating backups.

3. Removed removeSensitiveData from database_backup_details_uuid:
   I removed this call because it prevented access to the backup_id, which is necessary for identifying the correct backup configuration.