Create a deployment migration string #77

New issue

Open

opened 2025-01-27 13:18:52 +01:00 by fricklerhandwerk · 0 comments

fricklerhandwerk commented

2025-01-27 13:18:52 +01:00

Owner

As an operator,
given I want to migrate to a different Fediversity environment (#100),
I want to take my data out of the old environment,
so that I may move it to the new one (#78).

implementation notes

steps needed:

presuming the migration target host differs from the source host, from the source host:
1. create a back-up (#123)
2. create a back-up bucket key (nix) (c.f. #123) accessible by the new host
create a migration string, a JSON representation of the migration data model entry (#514), containing:
1. to reproduce the deployment, the deployed (panel: + staged?) configuration
2. the application state, i.e. the endpoint to the back-up on the created bucket along with its access/secret key taken from the earlier step

**As** an operator, **given** I want to migrate to a different Fediversity environment (#100), **I want** to take my data out of the old environment, **so that** I may move it to the new one (#78). ## implementation notes steps needed: 1. presuming the migration target host differs from the source host, from the source host: 1. create a back-up (#123) 1. [create a back-up bucket key](https://garagehq.deuxfleurs.fr/documentation/quick-start/#creating-buckets-and-keys) ([nix](https://git.fediversity.eu/Fediversity/Fediversity/src/commit/09119803e8731b123313641bbfc5a81d16b78f0f/services/fediversity/garage/default.nix#L70-L72)) (c.f. #123) accessible by the new host 1. create a migration string, a JSON representation of the migration data model entry (#514), containing: 1. to reproduce the deployment, the deployed (`panel`: + staged?) `configuration` 1. the application state, i.e. the endpoint to the back-up on the created bucket along with its access/secret key taken from the earlier step