feat: AWS S3 sync compatible exclude patterns #50
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.
Summary
*
now matches path separators, matching AWS CLI behaviorDetails
Problem
The current exclude pattern implementation using doublestar follows standard Unix glob behavior where
*
does not match path separators. This differs from AWS S3 sync which uses Python fnmatch where*
matches everything including/
.For example:
--exclude "_next/*"
only excludes_next/file.txt
--exclude "_next/*"
excludes_next/file.txt
,_next/subdir/file.txt
, etc.Solution
Ported Python fnmatch module to Go, maintaining the exact pattern matching behavior for AWS S3 sync compatibility.
Changes
Breaking Change
*
now match across directory boundaries.Test plan
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com