Manage repositories, channels, and settings from the TUI #1
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/tui-config-management"
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?
Summary
Extends the daemon's overlay mechanism (previously jobs/schedules only) to
repositories, notification channels, and service/maintenance settings, so
the TUI can create, edit, and delete all configuration over gRPC instead of
requiring hand-edits to
kbackup.yaml. All edits persist to the daemon'soverrides.yamland survive restart; the base config file is never rewritten.Changes
and body text. Dark-first preserved.
Name (textinputs were never
Focus()ed); fixed viaapplyFocus().RepoService.Upsert/Delete/GetRepository; full-schema form(local/s3/sftp) with a
bubbles/filepickerfolder browser; in-place edit withthree-state secret handling (keep blank / replace /
ctrl+xclear); live-appliedthrough a lock-guarded registry.
NotifyService.Upsert/Deletewith a new/edit/deleteform; live-applied via a mutex-guarded
notify.Dispatcher.SetChannels.SettingsService+ Settings tab. Maintenance windows andprune/scrub tunables apply live; log level / max jobs persist for restart;
state_dir/ipc_endpointstay base-owned (never repointed by the overlay).(would otherwise fail validation and brick daemon startup). Upserts persist
with rollback so disk and memory never disagree. Switching sftp auth
(password<->key) force-clears the inapplicable secret so a stale credential is
never resurrected.
Testing
go build ./...,go vet ./...,gofmt -lclean. New tests: overlay merges(repos/channels/service singleton), gRPC persistence round-trips across restart,
repo focus/validation/secret-clear, and
SetChannelsunder-race. Per projectpolicy, no host-mutating (VHD/DISM/VSS/mount) tests were run.
kReview review
Verdict: no findings
No findings to address in the reviewed diff.
No meaningful correctness, security, or persistence defects are provable from the visible diff and supplied context.
Reviewed by kReview at
db21dd21b8. This comment is conservative and based only on the PR diff and metadata.Est. cost ~$4.65 total (775.9k in / 29.6k out) · this run ~$0.73 (123.6k in / 4.4k out) / gpt-5.6-sol.