Follow-up from "Geo: run Geo migrations on secondary, instead of Rails migrations"
The following discussion from !1055 (merged) should be addressed:
-
@ibaum started a discussion: This step is currently failing due to a missing secret
gitlab-geo-geo-postgresql-password
. Creating ageo.psql.password
block in the settings file with an existingsecret
andkey
entry works around the issue.