-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Add ability to invalidate cloudfront assets #920
Comments
+1 |
1 similar comment
+1 |
The workaround IIUC is
http://docs.aws.amazon.com/cli/latest/reference/cloudfront/create-invalidation.html Which is awkward to use. |
I am now using the cloudfront-invalidator command line. It's crazy that this issue remains unresolved for aws-cli. No, I don't want to create JSON for a simple task. |
+1 |
2 similar comments
+1 |
👍 |
Thanks for the feature request. Just want to let you know that we hear you and have added a note to our backlog to look into this. |
+1 |
+1, that would be super awesome to use the official tool instead of s3cmd. |
Looks like the PR wasn't linked to this issue. PR: #1662 If you have any feedback on the proposed interface, feel free to comment on the PR. |
I was hoping that say upon a I'm not sure what or if there is a cost associated to invalidating the whole cache as opposed to the path. |
Thanks for the suggestion @kaihendry . We did think about the possibility of closer integration with the We will definitely keep seeking better solution for the this feature. Meanwhile we are also exciting to provide the long-awaited fundamental feature as a solid first step. Thank you everyone again, for all your support and patience. |
Thanks for tackling this issue! Just like @kaihendry I want to point out, that this issue is not fixed in the sense of the original request and the people 👍'ing. The "fix" added some syntactic sugar to This ticket is actually about not needing to deal with manual invalidation. Exactly the opposite, Should I create a separate ticket for that? |
@aronwoost is exactly right! This issue should not have been closed. |
Agree, please re-open. |
Using s3cmd I can write:
A similar option for
aws s3 cp/sync
would be helpful.The text was updated successfully, but these errors were encountered: