Skip to content

ShareSpec.DeleteData — opt-in full subvolume removal (#57)#5

Merged
ChrisonSimtian merged 1 commit into
mainfrom
feat/sharespec-deletedata
May 31, 2026
Merged

ShareSpec.DeleteData — opt-in full subvolume removal (#57)#5
ChrisonSimtian merged 1 commit into
mainfrom
feat/sharespec-deletedata

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator

Follow-up from the live smoke test, which confirmed DSM shares are btrfs subvolumes: the reconciler's safe default delete (synoshare --del FALSE, keep data) leaves the subvolume behind, and plain rm on it fails even as root.

  • ShareSpec.DeleteData (default false) — opt-in to a destructive synoshare --del TRUE that removes the data/subvolume too.
  • Reconciler wires it through and labels the plan reason keep data vs incl. data.
  • Tests for both delete modes (14 tests total).

Default behaviour is unchanged (keep data). 🤖 Generated with Claude Code

…#57)

The live smoke test confirmed DSM shares are btrfs subvolumes, so the safe
default delete (`synoshare --del FALSE`, keep data) leaves the subvolume
behind. Add an opt-in DeleteData flag (default false) that emits
`--del TRUE` for a destructive, data-removing delete.

- ShareSpec.DeleteData (default false); reconciler wires it through and
  labels the plan reason "keep data" vs "incl. data".
- Tests for both delete modes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian merged commit c1d3452 into main May 31, 2026
1 check passed
@ChrisonSimtian
ChrisonSimtian deleted the feat/sharespec-deletedata branch May 31, 2026 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant