Add support for Cloud SQL replication for Geo
What does this MR do?
MR adds support for Cloud SQL replication for Geo.
With GCP Cloud SQL a replica must be deployed in the same VPC and the same Project. This MR adds support following these limitations accordingly by adding support for the following:
- Ability to a Geo Replica via a separate Terraform state within the same VPC and Project
- Deploying a separate Geo Tracking database in Cloud SQL if desired
- Updating Ansible logic to better handle a separate Geo Tracking DB when no Praefect DB
- Refactor of internal networking references to be more consistent
Related issues
Closes #835 (closed) #321 (closed)
Author's checklist
When ready for review, the Author applies the workflowready for review label and mention @gl-quality/get-maintainers
:
- Merge request:
-
Corresponding Issue raised and reviewed by the GET maintainers team. -
Merge Request Title and Description are up-to-date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline -
MR has no new security alerts in the widget from the Secret Detection
andIaC Scan (SAST)
jobs.
-
- Code:
-
Check the area changed works as expected. Consider testing it in different environment sizes (1k,3k,10k,etc.). -
Documentation created/updated in the same MR. -
If this MR adds an optional configuration - check that all permutations continue to work. -
For Terraform changes: set up a previous version environment, then run a terraform plan
with your new changes and ensure nothing will be destroyed. If anything will be destroyed and this can't be avoided please add a comment to the current MR.
-
-
Create any follow-up issue(s) to support the new feature across other supported cloud providers or advanced configurations. Create 1 issue for each provider/configuration. Contact the Quality Enablement team if unsure.
Edited by Grant Young