Geo role hardcodes database user on secondary servers
- GET version: 2.8.5
- Cloud Provider: AWS
- Environment configuration: 3k Geo
We're using a database user different than gitlab
on my environment. We were able to set up a primary and a secondary site without any problems. But after running the geo playbook gitlab-rails was failing due to postgres authentication issues. The read-only-replica template has the database user hardcoded to gitlab
on it. And because it is included at the end of the main gitlab.rb
it overwrites the setting.