Fix access scopes on postgres-dr-delayed-01-db-gprd
During a recent terraform pipeline run, the following change was identified in the plan, and blocked during apply due to the allow_stopping_for_update
variable being set to false. We need to manually reconcile the access scopes on the instance and/or schedule a production change when we can stop the instance and perform the update
Terraform will perform the following actions:
1587 # module.postgres-dr-delayed.google_compute_instance.instance_with_attached_disk[0] will be updated in-place
1588 ~ resource "google_compute_instance" "instance_with_attached_disk" {
[...]
1827 ~ service_account {
1828 email = "terraform@gitlab-production.iam.gserviceaccount.com"
1829 ~ scopes = [
1830 - "https://www.googleapis.com/auth/cloud-platform",
1831 + "https://www.googleapis.com/auth/cloud.useraccounts.readonly",
1832 + "https://www.googleapis.com/auth/cloudkms",
1833 + "https://www.googleapis.com/auth/compute.readonly",
1834 + "https://www.googleapis.com/auth/devstorage.read_only",
1835 + "https://www.googleapis.com/auth/logging.write",
1836 + "https://www.googleapis.com/auth/monitoring.write",
1837 + "https://www.googleapis.com/auth/pubsub",
1838 + "https://www.googleapis.com/auth/service.management.readonly",
1839 + "https://www.googleapis.com/auth/servicecontrol",
1840 + "https://www.googleapis.com/auth/trace.append",
1841 ]
1842 }
1843 timeouts {}
1844 }