Option to avoid checking for file existence before deletion.

[reichertm]

I'm using Paperclip with Amazon S3 and a request to delete the paperclip file (file.destroy) results in 2 AWS request for each file style. First is a HEAD request, another is the actual DELETE request. It seems like this happens because each file style is checked for existence before being scheduled to be deleted. As far as I understand it happens in queue_all_for_delete method: https://github.com/thoughtbot/paperclip/blob/master/lib/paperclip/attachment.rb#L563

If possible it might be a good idea to have an option to delete a file without prior checking for existence. It would be useful when the result is not important and would halve the S3 bill (the requests quickly add up when cleaning up large number of files) and reduce the operation time.

[morgoth]

To actually avoid adding yet another option, wouldn't be better to always try to delete the file and catch errors for non existent ones?

[reichertm]

Sure, if only this is good enough for all the supported types of storage.

[sidraval]

Thank you for reporting this. Unfortunately, we will be deprecating Paperclip and therefore will not have the bandwidth to address this issue.