AWS S3Upload task add --sync or equivalent operation

[coffeedome]

Describe the bug

Task isn't overwriting files that already exist

To reproduce

Run S3 Upload task in yaml pipeline to a bucket with a target file that already exists.

Expected behavior

Existing files should be overwritten.

Screenshots

Your Environment

• On-prem or cloud based?: Cloud
• Azure DevOps version: Cloud
• AWS Toolkit for Azure DevOps version: Cloud

Additional context

[hunterwerlla]

Hello, can you provide additional information like logs?

The toolkit just uses an S3 PutObjectRequest which will always overrides unless the bucket is versioned, so I'm struggling to think that it could cause an issue with that

[j0nathontayl0r]

I'd assume the bug report is incorrectly written, the package successfully copies and replaces files with the same object name. But if an object is deleted at the source (e.g. an Azure DevOps repo), the destination S3 bucket doesn't perform the same action since, as intended. This is only copying the files, it's not performing sync with the additional --delete parameter.

The reporter may not have noticed the above and that the S3 object has changed names between source/destination.