Declarative full-config export / import (GitOps) #23
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rbrooks/Iris-WLED#23
Loading…
Add table
Add a link
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?
Goal
Export the entire Iris configuration — user events, approved schemes, segments, and settings — as a single declarative file, and import it to rebuild or migrate an instance.
Why it's valuable
The existing export is WLED-
presets.json-shaped (device state), not Iris state. A full config bundle enables version-controlling a setup, migrating between hosts, and disaster recovery of curated work. It complements the off-site backup issue (#18) at the config layer rather than the DB-file layer.Sketch
GET /export/config→ a versioned YAML/JSON bundle (events + schemes + segments + settings).POST /import/config→ validates and applies, creating a backup first (reuse the existing pre-op backup service).Acceptance criteria
Proposed enhancement (brainstorm follow-up).