Closed jimklimov closed 2 months ago
I think the zfs aproach #637 is sensible ... do you see benefit in this still ?
Somewhat yes. Properties allow for default settings, CLI options for run-time decisions. And this PR allows the latter to be consistent when nested datasets are involved :)
For example, avoid unexpected creation of avoidably large replicas of root datasets where promotable clones of boot environments are used (currently
znapzend
makes a new fullzfs send
, not a clone+promote operation - see #503 and others after it).Also added a
--noautoCreation
option to help override configuration file settings (where used), primarily to help test this change locally.NOTE: I have a nagging feeling that the default value for this setting belongs in ZFS properties (per-destination) rather than in CLI as one toggle to rule them all (can be kept for one-off overrides). Maybe another PR would address that, more so if I get to solving #503 directly. UPDATE: See #637 for zfs props approach.