handle multiple/missing destinations better #22
Labels
No Label
?/support
accepted
bug/defect
design flaw
design note
duplicate
enhancement
fix in dev
help wanted
invalid
needs info
rejected
feedback?
upstream
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ITwrxOrg/EZ-Bkup#22
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Right now, EZ-Bkup throws an error if any Destinations don't exist, which means one has to remove any Destination from the Routine that they don't want to use for that particular Bkup run, and re-add the missing destination later if they want to use it again. Using different Destinations for the same Routine is a common use case and should be better supported. Perhaps just continue Bkup as long as at least one Destination is available for the Routine, and log missing Destination(s). Maybe the "Bkup complete" message should say "Bkup complete with warnings logged."