Object Store Versioning

Received an email from the optimize team about api enabled bucket usage and object store versioning.

Issue: when copying data to an object store bucket through the api, and the object already exists, object storage in this scenario will create a new version for that file. Versions do eventually expire, however an audit has revealed that there are a lot of files with an excessive number of versions. This impacts costs as each version is a duplicate of the file.

In discussions with the optimize team, I have asked them to set the version retention policy on our buckets to 7 days. This means when we do create a duplicate file, it will only persist for 7 days.

**Longer Term Resolution**: Modify how files are getting copied to object storage and configure so that versions are not created unless explicitly stated

Start by identifying the API path that copies files to object storage and the version-retention policies on the affected buckets. Confirm how existing objects are replaced and whether callers can explicitly request versioning. Done means duplicate versions are not created by default, while explicitly requested versions still work, with the seven-day policy documented or verified.

Written by the indexing model from the issue text.