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

Allow custom invalidation path for cloudfront #21

Closed
mynomoto opened this issue Feb 10, 2016 · 3 comments
Closed

Allow custom invalidation path for cloudfront #21

mynomoto opened this issue Feb 10, 2016 · 3 comments

Comments

@mynomoto
Copy link
Contributor

Sometimes it may be better to invalidate /* than to invalidate many paths (costs maybe)

@martinklepsch
Copy link
Member

@mynomoto is Amazon really billing only a single path if you supply a wildcard? They have the same work to do as if you supply all paths separately...

@mynomoto
Copy link
Contributor Author

They say they do:
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#invalidation-specifying-objects-paths

The charge to submit an invalidation path is the same regardless of the number of objects you're invalidating: a single object (/images/logo.jpg) or all of the objects that are associated with a distribution (/*). For more information, see Amazon CloudFront Pricing.

It's not that important unless someone is generating html from templates and the base is always changing.

@martinklepsch
Copy link
Member

@mynomoto a PR to supply a custom invalidation path via an option is welcome!

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