feat(backup): export the account settings and restore them onto the account

Both backup purposes now carry an accountSettings section. The restore writes
it to the account being restored inside the same transaction, names every
refused value under the new accountSetting skip catalogue, and re-warms the
stored texts after the transaction when a unit preference changed, the way the
unit settings routes do. A file without the section leaves the account row as
it is, which is how every older backup restores. The instance settings
restore stays its own opt-in.
This commit is contained in:
Marc-André Bombeck committed 2026-10-01 13:04:41 +02:00
1 parent d731a1b8fe
commit 7abaa25c14
15 files changed
+159 -2

No files matched your search

+3
View File
@@ -467,6 +467,9 @@ function catalogueLabel(
if (catalogue === "scheduleRevisionLink") {
return t("admin.section.backups.restoreSkippedScheduleRevisionLink");
}
if (catalogue === "accountSetting") {
return t("admin.section.backups.restoreSkippedAccountSetting");
}
// Not a fallback: the chain above is exhaustive and this line is what makes
// the compiler say so. A catalogue added without a label here now stops the
// build instead of shipping under a label that belongs to something else,