sync: document --delete behavior for excluded files #4937
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running
aws s3 sync --delete ...
will not delete files that areexcluded by filters. For example:
aws s3 mb s3://sync-delete-exclude mkdir /tmp/sync-delete-exclude touch /tmp/sync-delete-exclude/{1,2,3,4} aws s3 sync /tmp/sync-delete-exclude s3://sync-delete-exclude # no files will be deleted: aws s3 sync s3://sync-delete-exclude /tmp/sync-delete-exclude \ --exclude=3 --exclude=4 --delete --dryrun
This is not immediately obvious from the documentation provided, and the
interaction between exclusion filters and the
--delete
strategy flagshould be explicitly stated.
solves the documentation issue with #4923.