Utilize this epic to track the necessary work to enable Deployer to perform controlled deployments into the secondary-site in the staging environment. To complete this, we'll need some minor chef improvements and some work performed on the CI pipeline of Deployer. This work can be considered complete when auto-deploys successfully deploy to the secondary site. ### Problem Statement Our current deploy mechanism doesn't have any information regarding the Geo functionality of GitLab. Due to this our current deploy methods will not sufficiently ensure that a secondary-site is deployed too properly. Currently, our deployments to the secondary-site are handled by chef upon the next chef run after a successful deployment has occurred. As the secondary-site is expanded into a multi-node environment, it will become much more important that we finely control the deployment to the secondary site, just as we deploy to the current primary-site. ### DRI @skarbek as a member of the ~"wg-disaster-recovery" ### Board TODO ### Status :black_large_square: (not started) Currently ~blocked awaiting decision to be made regarding the expansion of the staging environment. Issues for this would be located in parent epic https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/371 ### Exit Criteria * [ ] Necessary changes to chef are complete * [ ] Update to the deploy-tooling are complete * [ ] Auto-deploy successfully deploys, in a controller manner, to the secondary-site