Skip to content

Weird configuration needed on gitaly servers to enable server side repository backups on S3 compatible storage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

I tried adding this:

gitaly['configuration'] = {
  backup: {
    go_cloud_url: 's3://oc-sys-infra-gitaly-gitlab4-repo-backup',
    endpoint: 'https://s3.<company.domain.name>',
    s3ForcePathStyle: 'true',
    region: 'us-east-1'
  },

to the config on our gitaly servers, but got some error messages where the relevant part seemed to be Invalid region: region was not a valid DNS name.. Through asking for help on the community forum (https://forum.gitlab.com/t/configuring-gitaly-for-server-side-repository-backups-to-s3-compatible-storage/128836), I was advised to combine it into one line, and weirdly:

  backup: {
    go_cloud_url: 's3://oc-sys-infra-gitaly-gitlab4-repo-backup?endpoint=https://s3.<company.domain.name>&s3ForcePathStyle=true&region=us-east-1'
  },

worked. (I have since removed the strange &region=us-east-1 part, I just put it there to please things that validate the config - we're not actually in the US, but I believe that is the default value in many cases - it's not used with local S3 compatible storage) So when the configuration is split into multiple lines as the documentation suggests it doesn't work?

Edited by 🤖 GitLab Bot 🤖