Yeah seems a bit ridiculous to call this a feature proposal and not a bug report - a feature that was stated as working and a part of the GitLab application has been removed without warning. To make matters worse, that feature is many users fallback plan in case of data loss (such as in @burakcalik's case).
I'm setting up a client on Google Cloud currently and so far there's not a way to back up anywhere, which is a real deal-breaker.
By the sounds of https://gitlab.com/gitlab-org/gitlab-ce/issues/23043, the reasoning for not including support is based on how big the gem is. That seems like quite a weak reason for such an important feature for many users.
To confirm, does GitLab see AWS as the only true home for GitLab to run (given backups are an integral part of any production deployment)? That seems very counter to the impression I've had so far of GitLab.
May I ask, is it still possible to backup to GCS using the S3 API? Or will this now fail after the removal of fog-google? From what I can see, google-api-client is needed for full support, but without fog-google now, will we not be able to backup directly to GCS at all?
I'm pretty sure you were using the S3-like credentials (i.e. google_storage_access_key_id / google_storage_secret_access_key), right? This strategy was indeed working, and I'm sorry we didn't know that before. I will make sure to improve the documentation about that so that we don't do the same mistake twice. Google Cloud Storage support will be back in 8.15.4.