Different behavior when uploading a file with the same filename between v2 and v3

[xuuyswfaynvifuwm]

In our system we rely on filenames to generate consistent download URLs from S3.

In Carrierwave v3 the deduplicate mechanism generates filenames suffix, and I understand that it's related to this change, but it breaks our system when upgrading to v3.

Expected behavior (as of v2.2.5):

1. Upload dummy_file.pdf
2. See dummy_file.pdf in S3 folder
3. Re-upload dummy_file.pdf
4. See dummy_file.pdf in S3 folder

Current behavior (v3.1.2):

1. Upload dummy_file.pdf
2. See dummy_file.pdf in S3 folder
3. Re-upload dummy_file.pdf
4. See dummy_file(2).pdf in S3 folder

We managed to implement a workaround in our system with this file uploader:

class FileUploader < CarrierWave::Uploader::Base 

  def deduplicated_filename
    filename
  end

end

Would it be possible to at least have an "overwrite" option that would rename the new file to match the expected filename ? That would be a step 6 in the process explained here.

[justinbarclay]

My system ran into the same issue; I was using S3's versioning to track and revert files as needed. I also came up with the above workaround.

[mshibuya]

Obviously this is intentional. See #1855.