New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

--dry-run doesn't work properly with sync #1407

Open

Yanpas opened this issue Dec 6, 2024 · 1 comment

Yanpas commented Dec 6, 2024

It stops on the first entry to be synced and I don't see the full list of files to be synced

Contributor

snosratiershad commented Jan 13, 2025

@Yanpas I've tested sync with --dry-run and I see the full list of files:

$ s3cmd sync s3://salar-test/dir1/ s3://salar-test/dir2/ --dry-run
Summary: 2 source files to copy, 0 files at destination to delete
remote copy: 's3://salar-test/dir1/hello' -> 's3://salar-test/dir2/hello'
remote copy: 's3://salar-test/dir1/hi' -> 's3://salar-test/dir2/hi'
WARNING: Exiting now because of --dry-run

could you please provide more info like s3cmd version, your command and your output?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment