Modify the Geo setup instructions to copy gitlab-secrets.json between primary and secondary
The primary has many secrets that the secondary needs as well. Currently, we include instructions to manually copy some of them to the secondary, and also tell the user to keep track of one (DB replication password) themselves and manually enter it multiple times.
The database replication password is going into gitlab-secrets.json as part of the omnibus FDW effort. We can simplify our setup and instructions (and fix a number of DR bugs) by instructing the user to copy gitlab-secrets.json from primary to secondary.
This will need to happen after we've finished setting up the primary as the instructions include a number of steps that add / generate secrets.
Original description:
From Sid's demo, raw notes https://docs.google.com/document/d/1-93kEWlL5npXcrgS1moEkzSwkUODVLpN4C6KC_S7YFM/edit, point 22,
"Why do I need to supply the replication user password again and again? Why can't it store that."
I also recall from my own experience setting this up that it was not clear to me how/where to store this password. I use a password manager to generate and store passwords. Should the replication user password be treated as any user ID (ID name then?) and its corresponding password? And should that be available to all admins of the GitLab instance? So:
- is there a way to have the setup script store the replication password, at least per instance (iirc we need it first on the primary where we set it, then on the secondary where we use it)
- document more about what the replication user is and what to do with the password.