rdelaage
/
restic
mirror of https://github.com/restic/restic.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3103 from greatroar/rephrase-pr3102 

Rephrase #3095/#3102 changelog entry
This commit is contained in:
rawtaz 2020-11-17 12:52:12 +01:00 committed by GitHub
parent 1b6e8c888f 028f2b8c0e
commit 342520b648
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
changelog/unreleased/issue-3095
View File

@ -1,9 +1,17 @@
Change: Remove `--drive-use-trash=false` from default rclone params Change: Deleting files on Google Drive now moves them to the trash
By default restic used launched rclone with --drive-use-trash=false, When deleting files on Google Drive via an rclone backend, restic used
since google drive trash retention policy changed, it is no longer required. to bypass the trash folder and required using the `-o rclone.args`
Rclone will now use what's provided in by the `--drive-use-trash option to enable the trash folder. This ensured that deleted files in
parameter, `drive-use-trash` config or RCLONE_CONFIG_*_USE_TRASH env Google Drive were not kept indefinitely in the trash folder. Since
falling back to `true` as a default (as of: v1.53.2). Google Drive's trash retention policy changed to deleting trashed files
after 30 days, this is no longer needed.
https://github.com/restic/restic/issues/3095 Restic now leaves it up to rclone and its configuration to use or not
use the trash folder when deleting files. The default is to use the
trash folder, as of rclone 1.53.2. To re-enable the restic 0.11 behavior,
set the `RCLONE_DRIVE_USE_TRASH` environment variable or change the
rclone configuration. See the rclone documentation for details.
https://github.com/restic/restic/issues/3095
https://github.com/restic/restic/pull/3102