Skip to content
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.

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

aws s3 fails if non-existent soft link #781

Closed
woodnt opened this issue May 17, 2014 · 1 comment
Closed

aws s3 fails if non-existent soft link #781

woodnt opened this issue May 17, 2014 · 1 comment
Labels
bug This issue is a bug. s3sync

Comments

@woodnt
Copy link

woodnt commented May 17, 2014

Hello,

aws s3 fails if there is a symlink to a non-existent file. The expected behavior is to simply skip the file, but it results in complete failure of the script.

Here is an output example:

# aws s3 sync /root/ s3://HIDDEN/root/ --exclude "/root/bin/*" 2> /tmp/errors
[Errno 2] No such file or directory: '/root/hello' 
Completed 1 part(s) with ... file(s) remaining

Regards,
Nathan

@jamesls
Copy link
Member

jamesls commented Aug 1, 2014

Closing, this was implemented via #854 and now part of the latest CLI release.

@jamesls jamesls closed this as completed Aug 1, 2014
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. s3sync
Projects
None yet
Development

No branches or pull requests

2 participants