关于“使用 Cloud Run 构建可创建 PDF 文件的无服务器应用”的评价

Juan Diego N. · 已于 about 1 month前审核

Ian S. · 已于 about 1 month前审核

Done

Anil B. · 已于 about 1 month前审核

Peter I. · 已于 about 1 month前审核

Jeyson G. · 已于 about 1 month前审核

Yousif A. · 已于 about 1 month前审核

Jesus Humberto A. · 已于 about 1 month前审核

André M. · 已于 about 1 month前审核

Pier Luigi B. · 已于 about 1 month前审核

No clean steps . a step in I AM binding to service account. Service account name is given wrong

Indhu P. · 已于 about 1 month前审核

Vaibhav T. · 已于 about 1 month前审核

Nitesh R. · 已于 about 1 month前审核

Xiao Qing K. · 已于 about 1 month前审核

Revi G. · 已于 about 1 month前审核

Priyanka S. · 已于 about 1 month前审核

rajkumar n. · 已于 about 1 month前审核

Anton T. · 已于 about 1 month前审核

nice

Sergio M. · 已于 about 1 month前审核

Juan pablo A. · 已于 about 1 month前审核

Nidhi S. · 已于 about 1 month前审核

muy poco timepo

Juan pablo A. · 已于 about 1 month前审核

Nidhi S. · 已于 about 1 month前审核

Dockerfile seems is not properly updated to run when deploying in cloud run.

Neptali D. · 已于 about 1 month前审核

Satin M. · 已于 about 1 month前审核

Overall Feedback: Great lab on event-driven architecture with Cloud Run and Pub/Sub, but there are two significant IAM/service account blockers in Task 4 that prevent users from completing the steps as written. Issue 1: Missing permission for Cloud Storage to publish to Pub/Sub Description: When running the gsutil notification create command, it fails with a BadRequestException: 400 because the Cloud Storage service account lacks permission to publish to the newly created new-doc topic. Suggested Fix: Please update the instructions to explicitly grant the roles/pubsub.publisher role to the Storage Service Agent before creating the notification. Code fix: Bash GCS_SA=$(gcloud storage service-agent) gcloud pubsub topics add-iam-policy-binding new-doc \ --member="serviceAccount:$GCS_SA" \ --role="roles/pubsub.publisher" Issue 2: Pub/Sub Service Agent does not exist when applying IAM permissions Description: When attempting to grant the iam.serviceAccountTokenCreator role to the Pub/Sub service account (service-[PROJECT_NUMBER]@gcp-sa-pubsub.iam.gserviceaccount.com), the command fails with INVALID_ARGUMENT: Service account... does not exist. Enabling the Pub/Sub API does not provision this identity fast enough (or at all) in the lab environment. Suggested Fix: Please add a command to explicitly force the creation of the Pub/Sub service identity prior to the IAM binding step. Code fix: Bash gcloud beta services identity create --service=pubsub.googleapis.com --project=$GOOGLE_CLOUD_PROJECT Minor Note on Deprecation: The lab still relies heavily on gsutil mb and gsutil notification create, which throws multiple console warnings recommending the newer gcloud storage CLI. Updating these to gcloud storage buckets create would make the output cleaner for students.

Sangeeth P. · 已于 about 1 month前审核