Option to skip existing files when copying to S3

Created on 18 July 2016, over 8 years ago
Updated 4 January 2025, 5 days ago

Since we have knowledge of which files exist on S3 from the local metadata cache, I think we should add an option to NOT transfer local files already existing on S3.

For example, we have about 16 GB of files that we're pushing up to S3. We're doing this in a staging environment first, and then we'll do it again after we've tested that our S3 File System configuration is working properly. But that takes a really long time, so we'd like to skip copying any existing files on subsequent tests.

I'll submit a patch shortly.

✨ Feature request
Status

Closed: outdated

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States joelstein

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States cmlara

    Drupal 7 end-of-life triage:
    Drupal 7 will reach end of life on January 5th.

    The 7.x branches of S3FS do not have any additional planned releases.

    The features requested in this issue have already been implemented in the the 8.x-3.x and newer releases.

Production build 0.71.5 2024