restore command and label design #42

New Issue

3wordchant · 2023-11-12T01:10:56Z

3wordchant commented

2023-11-12 01:10:56 +00:00

In looking at #26, I'm wondering about the command-line interface to backup restore

Currently, it will try to restore either "everything on the server" (without -h) or "all volumes associated with an app" (if -h is set).

Personally, it would be useful to be able to restore a single service at a time – so for e.g. wordpress.example.com, being able to restore just the app service (i.e. the wordpress_content volume) or the db service (i.e. copying dump.sql.gz into the mariadb volume, then running the post-restore command to load it).

Additionally, at Autonomic, we will almost never want to restore an entire server, and we will rarely, if ever, need to restore secrets (although it's AWESOME that they are now backed up effectively through backupbot 😍). So, it would be nice if these options weren't the default.

So, I would like to propose the following CLI:

backup restore (STACK SERVICE|--all) [--secrets]

STACK      stack name, e.g. "wordpress.example.com"
SERVICE    service name, e.g. "app"

--all      restore all stacks and services
--secrets  restore secrets associated with the stacks and services to be restored

CC @moritz

In looking at #26, I'm wondering about the command-line interface to `backup restore` Currently, it will try to restore either "everything on the server" (without `-h`) or "all volumes associated with an app" (if `-h` is set). Personally, it would be useful to be able to restore a single service at a time – so for e.g. `wordpress.example.com`, being able to restore just the `app` service (i.e. the `wordpress_content` volume) or the `db` service (i.e. copying `dump.sql.gz` into the `mariadb` volume, then running the post-restore command to load it). Additionally, at Autonomic, we will almost never want to restore an entire server, and we will rarely, if ever, need to restore secrets (although it's AWESOME that they are now backed up effectively through backupbot 😍). So, it would be nice if these options weren't the default. So, I would like to propose the following CLI: ``` backup restore (STACK SERVICE|--all) [--secrets] STACK stack name, e.g. "wordpress.example.com" SERVICE service name, e.g. "app" --all restore all stacks and services --secrets restore secrets associated with the stacks and services to be restored ``` CC @moritz

👍 3

3wordchant added this to the backupbot revolution project 2023-11-12 01:11:50 +00:00

moritz commented

2023-11-23 20:24:45 +00:00

I like the idea of being able to choose the volumes/container to restore.

Secrets are only backed up at the moment. Without having the secrets you are not able to restore most database dumps without manually resetting the passwords. But there is still no automated secret restore function. This would need to be implemented into abra.

I like the idea of being able to choose the volumes/container to restore. Secrets are only backed up at the moment. Without having the secrets you are not able to restore most database dumps without manually resetting the passwords. But there is still no automated secret restore function. This would need to be implemented into `abra`.

decentral1se added the

help wanted

label 2024-01-11 13:32:34 +00:00

decentral1se referenced this issue from coop-cloud/abra

2024-01-12 15:50:28 +00:00

feat: backup revolution #361

decentral1se referenced this issue

2024-01-12 20:56:17 +00:00

post backup restore command #26

~~decentral1se referenced this issue from coop-cloud/organising 2024-03-12 09:58:16 +00:00~~

New abra release planning #583

decentral1se referenced this issue from coop-cloud/organising