S3 Invalidation #96
Open
S3 Invalidation #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Has the ability to send invalidation requests to CloudFront been implemented in another way in the gem by now? I couldn't anything related to invalidation in the gem's rdoc. This pull request is old, but I would love to see this functionality in the gem. |
|
Guess if this didn't make it in, then probably not. Feel free to make this merge properly in a new pull request and we can try to get it in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on this blog-post: http://wellconsidered.be/amazon-cloudfront-invalidation-for-appoxy-aws