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

--cf-invalidate doesn't invalidate copied files #525

Closed
rstacruz opened this issue Apr 9, 2015 · 2 comments
Closed

--cf-invalidate doesn't invalidate copied files #525

rstacruz opened this issue Apr 9, 2015 · 2 comments

Comments

@rstacruz
Copy link

rstacruz commented Apr 9, 2015

Let's say you have 3 identical files:

/files/v0/file.js
/files/v0.1/file.js
/files/v0.1.9/file.js

and you sync it using s3cmd sync:

s3cmd sync --cf-invalidate --acl-public --preserve --recursive ./files s3://my-cdn/

WARNING: Module python-magic is not available. Guessing MIME types based on file extensions.
./files/v0.1.9/file.js -> s3://my-cdn/files/v0.1.9/file.js  [1 of 1]
 37842 of 37842   100% in    1s    27.05 kB/s  done
remote copy: files/v0.1.9/file.js -> files/v0.1/file.js
remote copy: files/v0.1.9/file.js -> files/v0/file.js
Done. Uploaded 37842 bytes in 2.9 seconds, 12.81 kB/s. Copied 2 files saving 75684 bytes transfer.
Created invalidation request for 1 paths
Check progress with: s3cmd cfinvalinfo cf://.../...

It says it Created invalidation request for 1 paths, which should probably be 3.

@rstacruz
Copy link
Author

anyone got a workaround or resolution for this?

@fviard
Copy link
Contributor

fviard commented Dec 7, 2017

Should be fixed with:
aa18fa4

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

No branches or pull requests

2 participants