bloomreach / bloomreach/s4cmd

--delete-removed does not respect --dry-run for dsync

Open
#152 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
1.4k
Forks
209
PR merge metrics
No merged PRs in 30d

Description

Even with `--dry-run`, the `--delete-removed` option seems to delete the files on destination anyway.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `dsync` with `--delete-removed` and `--dry-run`, using a destination containing a removed file. Trace the deletion behavior and verify that a dry run leaves destination files unchanged while normal synchronization still deletes them.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.