Your organization uses a central CI/CD project named `proj-pipeline` hosting a deployment service account. This service account is configured to provision microservices inside a dedicated workload project named `proj-microservices-prod`. During the initial deployment execution, the pipeline fails with an error indicating that the Cloud Run API (`run.googleapis.com`) is not enabled. Following Google Cloud security and operational best practices, which action should be performed to resolve this issue?
- Enable the `run.googleapis.com` API inside `proj-microservices-prod` using an identity granted the Service Usage Admin (`roles/serviceusage.serviceUsageAdmin`) role on `proj-microservices-prod`.Cevap
- BEnable the `run.googleapis.com` API inside `proj-pipeline` using an identity granted the Service Usage Admin (`roles/serviceusage.serviceUsageAdmin`) role on `proj-pipeline`.
- CGrant the deployment service account the primitive Editor (`roles/editor`) role at the Organization level so that API enablement automatically inherits down to `proj-microservices-prod`.
- DSubmit a Cloud Quota increase request for Cloud Run API requests per minute under `proj-microservices-prod` to automatically enable the service.
Cevap
Enable the `run.googleapis.com` API inside `proj-microservices-prod` using an identity granted the Service Usage Admin (`roles/serviceusage.serviceUsageAdmin`) role on `proj-microservices-prod`.
In Google Cloud, API enablement is scoped to individual projects where resources reside. To deploy Cloud Run services in `proj-microservices-prod`, the `run.googleapis.com` API must be enabled on `proj-microservices-prod`. Using the predefined Service Usage Admin role adheres to the principle of least privilege.
Adım Adım Çözüm
Anahtar Kavram
Enabling and Managing Cloud Service APIs