New Feature of Emptying S3 Bucket (preferably used before the deploy to s3) #21
Conversation
This file contains hidden or 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
Owner
|
Apologies @pekevski, I missed this PR. I had a child in hospital back then so slipped my attention. Happy to reconsider if you like (though very late). |
Author
|
That's okay I was cleaning up my PR's in Github. Happy to reopen it if you like. My previous employer was using this and I think the use-case is valid for others. Happy to reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Internally we needed the requirement of emptying specific files from an S3 bucket before the deploy (with this plugin)
I thought it would be nice to add an extra goal of emptying an s3 bucket with the ability to exclude certain paths based on a list of regular expressions.
Thanks for the great plugin originally!