<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ## Background Features in the [package stage](https://about.gitlab.com/handbook/product/categories/#package-stage) make heavy use of uploads. There are two major ways [uploads](https://docs.gitlab.com/ee/administration/uploads.html) can be configured: 1. Local storage 1. Object storage With the object storage option, there are a variety of providers that can be used: 1. GCP Storage 1. AWS S3 1. Azure Blob Storage 1. MinIO. 1. Others There are also a variety of [settings](https://docs.gitlab.com/ee/administration/uploads.html#object-storage-settings) that can be used when using object storage: 1. `background_upload` 1. `proxy_upload` 1. `direct_upload` Looking at these options, it can be seen that any given GitLab instance could be configured in dozens of different ways. ## Proposal We have some ways of writing tests against the different object storage settings and testing object storage versus local storage, but I am not aware of any automated tests that allow us to test against the variety of object storage providers. If we could automate some of these tests, it could save time during development, and lower risk of a platform specific bug making it to production.