Config export / import (locations, channels, subscriptions as JSON) #79
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#79
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One-click backup/restore of the whole configuration, independent of the Postgres backup gap (F-28); also makes dev↔prod parity and disaster recovery trivial. Missed because a single operator hand-configures once and forgets the rebuild cost. Effort S, value Medium.
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding I-09.Done in #97 (merged). Admin
GET /api/config/exportreturns locations, notification channels, and subscriptions as JSON (full channel config — including secrets — so a restore is complete; flagged as sensitive), with a schema version.POST /api/config/importrecreates them with natural-key dedup (location by name+lat/lon, channel by name+type), additive by default (a gatedreplace=trueflag prunes absent items), triggering NWS re-resolution for new locations. Backup/restore UI added to the Settings page. Independent of the Postgres backup (#67) — good for dev↔prod parity and quick DR.